Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
jrmaiafs said:
Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
Click to expand...
Click to collapse
You still have twrp right. So a easy way is to download a toolkit from the moto x 2014 thread onto your PC and install it. Then boot your phone into bootloader/fastboot and make sure you also install the moto drivers which the toolkit will ask you to do. Then just follow directions using the toolkit and you will be back up n running. Or you can sideload a rom onto twrp using the 1.0.3.2 version of adb drivers. I have done it successfully many times using Linux but with Linux you just have to type a ./ in front of adb sideload rom.zip for it to work. Just don't worry. As long as you have a bootloader then your phone is never bricked. Toolkit is below...
http://forum.xda-developers.com/showthread.php?t=2897819
im glad to know that "As long as you have a bootloader then your phone is never bric
skulldreamz said:
You still have twrp right. So a easy way is to download a toolkit from the moto x 2014 thread onto your PC and install it. Then boot your phone into bootloader/fastboot and make sure you also install the moto drivers which the toolkit will ask you to do. Then just follow directions using the toolkit and you will be back up n running. Or you can sideload a rom onto twrp using the 1.0.3.2 version of adb drivers. I have done it successfully many times using Linux but with Linux you just have to type a ./ in front of adb sideload rom.zip for it to work. Just don't worry. As long as you have a bootloader then your phone is never bricked. Toolkit is below...
http://forum.xda-developers.com/showthread.php?t=2897819
Click to expand...
Click to collapse
Thank you for your help, but i dont have anymore twrp, and my phone is xt 1097, im glad to know that "As long as you have a bootloader then your phone is never bricked." i have it still!!
Now RSD Lite recognizes my phone, but when i start to flash android 5.0 it says: version downgraded for primary_gpt
I flash this same rom (5.0) before using RSD Lite and it worked perfectly, but now gives this error. How can i fix it?
Have you got your factory image for your phone and mfastboot?
yes, i have it
orangestrawberry said:
Have you got your factory image for your phone and mfastboot?
Click to expand...
Click to collapse
I heard many people reporting this error, say they have posts here on xda that solves the problem but I could not find them . I have seen in a blog that the problem is in doing downgrading from 5.0 to 5.1. and they say that to solve it is necessary to change two lines of a file , but I do not know which file is this , and not how it's done
jrmaiafs said:
Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
Click to expand...
Click to collapse
Can you get into bootloader mode (fastboot)? What version of the bootloader are you running (you can see this in bootloader mode)?
I have bootloader (fastboot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JulesJam said:
Can you get into bootloader mode (fastboot)? What version of the bootloader are you running (you can see this in bootloader mode)?
Click to expand...
Click to collapse
these are the information appearing:
So I try to install the rom 5.0 with RSD Lite this error occurs :
And that's what the RSD Lite says :
I was using the soak test 5.1 V : 23:11:14 , and went back to retail by 5.0 RSD Lite 6.2.4 , and is giving the following error "version is downgraded primary- gpt "
jrmaiafs said:
I was using the soak test 5.1 V : 23:11:14 , and went back to retail by 5.0 RSD Lite 6.2.4 , and is giving the following error "version is downgraded primary- gpt "
Click to expand...
Click to collapse
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Thank you
JulesJam said:
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Click to expand...
Click to collapse
There was no time I try your solution because I was looking for other answers before I saw your comment , I found the solution in this blog , anyway thanks for the help . but it is in Portuguese
http://motox-brasil.blogspot.com.br...howComment=1433025924130#c6945390347560261007
jrmaiafs said:
There was no time I try your solution because I was looking for other answers before I saw your comment , I found the solution in this blog , anyway thanks for the help . but it is in Portuguese
http://motox-brasil.blogspot.com.br...howComment=1433025924130#c6945390347560261007
Click to expand...
Click to collapse
Ok but all that says to do is to flash the 5.0 firmware with RSDLite. I thought that was what you were trying to do and were getting an error?
JulesJam said:
Ok but all that says to do is to flash the 5.0 firmware with RSDLite. I thought that was what you were trying to do and were getting an error?
Click to expand...
Click to collapse
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
3rdstring said:
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ah, got it.
So I am having this exact problem now and I think somewhere along the way I flashed files from the wrong version and now my phones seems to not recognize the system storage or doesn't know how to write to it. My bootloader is 60.18....I've tried the system files for 5.1 and 6.0 but nothing seems to work. After I enter all of the commands it just reboots over and over and says erasing...
really strange
JulesJam said:
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Click to expand...
Click to collapse
KB Smoka said:
So I am having this exact problem now and I think somewhere along the way I flashed files from the wrong version and now my phones seems to not recognize the system storage or doesn't know how to write to it. My bootloader is 60.18....I've tried the system files for 5.1 and 6.0 but nothing seems to work. After I enter all of the commands it just reboots over and over and says erasing...
really strange
Click to expand...
Click to collapse
Is your bootloader unlocked? Last I read you could get the Verizon Moto X 2014 bootloader unlocked.
You can get into bootloader mode and use fastboot commands, correct?
3rdstring said:
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Hi there 3rdstring, I don't suppose you could translate it to English for us, could you? Or I guess I can see if Google Chrome will do that.
Dangerous-Beans! said:
Hi there 3rdstring, I don't suppose you could translate it to English for us, could you? Or I guess I can see if Google Chrome will do that.
Click to expand...
Click to collapse
No worries, Chrome did the translating fine. )
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
Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
s code showed up in the picture.
Thanks for all,
Bruno Sastre.
BrunoX10 said:
Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
s code showed up in the picture.
Thanks for all,
Bruno Sastre.
Click to expand...
Click to collapse
Whoa buddy!!
As sad as this is, we have warnings posted in nearly every sub-forum in the Moto X section warning you not to downgrade.
Fortunately, you can still access fastboot so you MIGHT still have some hope, but it is hard telling.
Since the 4.4.3 full SBF for Brazil Retail has not been leaked it is going to be much trickier....
Here is my suggestion:
First, you say you tried to "downgrade" to 4.4.2, so this leads me to believe that you had the 4.4.3 Brazil Retail OTA on your phone.
Find a copy of the 4.4.2 brazil Retail OTA, and extract it. You will also need the entire 4.4.2 Brazil Retail SBF file (and VERIFY THE CHECKSUMS to make sure you do not have corrupted files).
I suggest you extract "gpt.bin" from the 4.4.3 OTA, and extract "motoboot.img" from the 4.4.2 OTA.
Now a little explaination: gpt.bin is "GUID Partition Table". Since we KNOW that you cannot attempt to downgrade gpt.bin OR Motoboot, we are using the MOST RECENT versions of both. The 4.4.3 OTA contained a new gpt.bin, but the most recent bootloader is still the 4.4.2 version.
The idea here is to flash JUST gpt.bin and motoboot.img, then immediately REBOOT, so that the bootloader can LOAD the new partition table BEFORE we flash any other partitions. Give it a shot:
mfastboot flash partition gpt.bin (USE GPT.BIN FROM THE 4.4.3 OTA FILE)
mfastboot flash bootloader motoboot.img
mfastboot reboot-bootloader
NOW, the following fastboot flash commands using the files from the 4.4.2 Brazil Retail SBF:
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 erase customize
mfastboot erase clogo
now reboot, assuming you were even able to get this far..... Your X already appears to be in awful shape, so I don't see how any of this could hurt you, but it just MIGHT work....
If this works, and you are actually able to get booted into android, DO NOT ACCEPT THE OTA. Doing so will possibly brick you again.
Instead, just wait until the full leaked 4.4.3 SBF is released, and THEN, you can consider trying to flash the ENTIRE 4.4.3 SBF, if you want to upgrade.
samwathegreat said:
Whoa buddy!!
As sad as this is, we have warnings posted in nearly every sub-forum in the Moto X section warning you not to downgrade.
Fortunately, you can still access fastboot so you MIGHT still have some hope, but it is hard telling.
Since the 4.4.3 full SBF for Brazil Retail has not been leaked it is going to be much trickier....
Here is my suggestion:
First, you say you tried to "downgrade" to 4.4.2, so this leads me to believe that you had the 4.4.3 Brazil Retail OTA on your phone.
Find a copy of the 4.4.2 brazil Retail OTA, and extract it. You will also need the entire 4.4.2 Brazil Retail SBF file (and VERIFY THE CHECKSUMS to make sure you do not have corrupted files).
I suggest you extract "gpt.bin" from the 4.4.3 OTA, and extract "motoboot.img" from the 4.4.2 OTA.
Now a little explaination: gpt.bin is "GUID Partition Table". Since we KNOW that you cannot attempt to downgrade gpt.bin OR Motoboot, we are using the MOST RECENT versions of both. The 4.4.3 OTA contained a new gpt.bin, but the most recent bootloader is still the 4.4.2 version.
The idea here is to flash JUST gpt.bin and motoboot.img, then immediately REBOOT, so that the bootloader can LOAD the new partition table BEFORE we flash any other partitions. Give it a shot:
mfastboot flash partition gpt.bin (USE GPT.BIN FROM THE 4.4.3 OTA FILE)
mfastboot flash bootloader motoboot.img
mfastboot reboot-bootloader
NOW, the following fastboot flash commands using the files from the 4.4.2 Brazil Retail SBF:
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 erase customize
mfastboot erase clogo
now reboot, assuming you were even able to get this far..... Your X already appears to be in awful shape, so I don't see how any of this could hurt you, but it just MIGHT work....
If this works, and you are actually able to get booted into android, DO NOT ACCEPT THE OTA. Doing so will possibly brick you again.
Instead, just wait until the full leaked 4.4.3 SBF is released, and THEN, you can consider trying to flash the ENTIRE 4.4.3 SBF, if you want to upgrade.
Click to expand...
Click to collapse
Since he's international, couldn't he unlock the bootloader and reflash the software image?
sivarticus85 said:
Since he's international, couldn't he unlock the bootloader and reflash the software image?
Click to expand...
Click to collapse
That's not what's at issue here. You don't even need to be unlocked to flash stock firmware because it is signed with release keys.
The issue is that he tried to downgrade. Read the stickies and you should understand.
samwathegreat said:
That's not what's at issue here. You don't even need to be unlocked to flash stock firmware because it is signed with release keys.
The issue is that he tried to downgrade. Read the stickies and you should understand.
Click to expand...
Click to collapse
I know he was trying to downgrade, but I didn't realize what had happened until I re-read his post. I get it now. I think what you suggested should do the trick.
Still working [I hope]
BrunoX10 said:
Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
s code showed up in the picture.
Thanks for all,
Bruno Sastre.
Click to expand...
Click to collapse
Hi Guys,
Master Samwathegreat!!!
I did flash gpt.bin from 4.4.3 OTA Retail BR and went fine but when I tryed motoboot.img - prompts says:
"(bootloader) Variable not supported!
target max-download-size: 768
sending 'bootloader' (1604 KB)...
OKAY [time]
writing 'bootloader' . . .
(bootloader) Permission denied
FAILED (remote failure)
finished. total time..."
So now I'm getting many firmwares to try flash motoboot.
Thanks for it man, I am still working on it and I ll send good news!! I hope.
BrunoX10 said:
Hi Guys,
Master Samwathegreat!!!
I did flash gpt.bin from 4.4.3 OTA Retail BR and went fine but when I tryed motoboot.img - prompts says:
"(bootloader) Variable not supported!
target max-download-size: 768
sending 'bootloader' (1604 KB)...
OKAY [time]
writing 'bootloader' . . .
(bootloader) Permission denied
FAILED (remote failure)
finished. total time..."
So now I'm getting many firmwares to try flash motoboot.
Thanks for it man, I am still working on it and I ll send good news!! I hope.
Click to expand...
Click to collapse
Try skipping that command. Can you run any of the other fastboot flash commands?
Definitely use caution. I recommend you don't try downgrading the bootloader.
Bad Feelings...
samwathegreat said:
Try skipping that command. Can you run any of the other fastboot flash commands?
Definitely use caution. I recommend you don't try downgrading the bootloader.
Click to expand...
Click to collapse
===================================================================================================
NOPE MAN!
Tryed others flash commands and no one hits.
at the same time, I got and tryed "TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml" too, but without sucess =///
RSD Lite + W8 sucks, cannot find device - and I m going to wallmart tomorow, one week stucked on it... no one desires...
Thank you Xda.
BrunoX10 said:
===================================================================================================
NOPE MAN!
Tryed others flash commands and no one hits.
at the same time, I got and tryed "TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml" too, but without sucess =///
RSD Lite + W8 sucks, cannot find device - and I m going to wallmart tomorow, one week stucked on it... no one desires...
Thank you Xda.
Click to expand...
Click to collapse
Can you tell me what error you get when you type, for instance:
fastboot flash system system.img
Good News - We made it!!!
samwathegreat said:
Can you tell me what error you get when you type, for instance:
fastboot flash system system.img
Click to expand...
Click to collapse
Yahh Man, you´r the one!
I´d just took a coffe [got high] and remake, prompt by prompt on new firmware downloaded from sbrf.
So we made it guys, the MX rebooted normaly and I really dont know how but worths as you said, skipping commands.
Thank you Samwathegreat!:good:
Thank you XDA Family.
BrunoX10 said:
Yahh Man, you´r the one!
I´d just took a coffe [got high] and remake, prompt by prompt on new firmware downloaded from sbrf.
So we made it guys, the MX rebooted normaly and I really dont know how but worths as you said, skipping commands.
Thank you Samwathegreat!:good:
Thank you XDA Family.
Click to expand...
Click to collapse
F-A-N-T-A-S-T-I-C !!!
I'm very glad you had success :highfive: (High-Five)
EDIT: @BrunoX10 can you read this post: http://forum.xda-developers.com/moto-x/moto-x-qa/request-twrp-backup-brazil-retail-t2817522
This user needs your help! He is also using Brazil Retail 4.4.3 and accidently erased /system
Can you help him by making a backup of /system and sharing?
Last night, my phone was running slow so I rebooted my phone. My phone started bootlooping (stayed in the bootloader warning screen).
Here's where it gets weird: I went into TWRP and tried a bunch of different solutions. I tried to create a nandroid and a bunch of error messages popped up like "E: unable to /mount". I tried factory reset and same error messages.
I was worried the bootloop would occur again so I pressed format data and without thinking, formatted my entire card.
Now I have a phone with no system, no backup, but still in the TWRP screen. Without doing more damage, where do I go from here?
Moto X 2014 Pure Edition with bootloader unlocked.
Looks like you're going to have to flash the factory images and start fresh.
Sent from my XT1095 using Tapatalk
Thanks for the quick reply. Can you guide me towards doing that?
You could go the factory image route (just google Motorola Factory Images and it'll be the first result. You need a motorola account to access them).
You can also boot into TWRP and transfer a ROM over via ADB if you want to stick with the custom ROMs. Just boot into TWRP and connect to your computer, then adb push the ROM file.
This is the error message I get when I tried to push a zip to my /sdcard directory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says it's a "Read-only file system".
You would unzip that file to get to the sparsechunks and then you would:
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
DocDroid said:
This is the error message I get when I tried to push a zip to my /sdcard directory:
It says it's a "Read-only file system".
Click to expand...
Click to collapse
I extracted the zip file into the same folder. I copied your first line of command and this has been my screen for the past 15 minutes:
Should it take that long? As a note, all the files you mentioned are there.
I extracted the zip file into the same folder. I copied your first line of command and this has been my screen for the past 15 minutes:
Should it take that long? As a note, all the files you mentioned are there.
d33dvb said:
You would unzip that file to get to the sparsechunks and then you would:
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
Click to expand...
Click to collapse
DocDroid said:
I extracted the zip file into the same folder. I copied your first line of command and this has been my screen for the past 15 minutes:
Should it take that long? As a note, all the files you mentioned are there.
Click to expand...
Click to collapse
Are you trying to flash those in recovery? You need to be in fastboot (bootloader) mode.
Sent from my XT1095 using Tapatalk
dustin_b said:
Are you trying to flash those in recovery? You need to be in fastboot (bootloader) mode.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
The rabbit hole goes deeper. I'm in bootloader mode, copy and paste the first line of command, and here's the new error:
Is your bootloader unlocked?
Did you reboot into bootloader from twrp? If so, power off there phone and not into fastboot that way. Then try it.
Sent from my XT1095 using Tapatalk
---------- Post added at 04:21 PM ---------- Previous post was at 04:21 PM ----------
d33dvb said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
It has to be since he had twrp.
Sent from my XT1095 using Tapatalk
d33dvb said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes, unlocked bootloader. Motorola Device Manager tells me my phone's current version is "22.21.11.victara_tmo.tmo.en.us" and I was running Lollipop 5.0 before it went beserk yesterday.
I downloaded the image file from http://www.graffixnyc.com/motox.php under the title "Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip."
I honestly don't know what is wrong!!
dustin_b said:
Did you reboot into bootloader from twrp? If so, power off there phone and not into fastboot that way. Then try it.
Sent from my XT1095 using Tapatalk
Just tried that. Powered off phone, held onto power button + down, entered bootloader mode, inputted first line of command, and still the same error message.
Click to expand...
Click to collapse
DocDroid said:
dustin_b said:
Did you reboot into bootloader from twrp? If so, power off there phone and not into fastboot that way. Then try it.
Sent from my XT1095 using Tapatalk
Just tried that. Powered off phone, held onto power button + down, entered bootloader mode, inputted first line of command, and still the same error message.
Click to expand...
Click to collapse
Do you have fastboot installed? If so, try using it instead of mfastboot. I had a problem like that once but I really don't know what fixed it. That's about the only other suggestion I have.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
dustin_b said:
DocDroid said:
Do you have fastboot installed? If so, try using it instead of mfastboot. I had a problem like that once but I really don't know what fixed it. That's about the only other suggestion I have.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
- I installed Minimal ADB and Fastboot tool found here.
- I placed the zip file in the "Minimal ADB and Fastboot" folder.
- I took all the commands from above and inputted.
- Error message: "Boot up failed. Invalid boot image header!"
HELP!
Click to expand...
Click to collapse
New development:
I flashed "TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip" using the commands given with success!
Figuring that this is it, I pressed "normal startup" and my phone is once again stuck in the "Warning Bootloader unlocked" screen. Has not gone to the Moto world animation screen yet.
Because u hav wiped ur entire os widout nandroid backup..u will hav to flash a rom(stock or custom..ur choice) again..Ensure u hav an unlocked bootloader..Download a rom frm the internet that suits ur device and place it on the root of sd card..then boot into twrp..wipe data and cache..click install and find ur image and click it..the rom will get flashed to ur device..
Sent from my Micromax A110 using XDA Free mobile app
REDswapnil said:
Because u hav wiped ur entire os widout nandroid backup..u will hav to flash a rom(stock or custom..ur choice) again..Ensure u hav an unlocked bootloader..Download a rom frm the internet that suits ur device and place it on the root of sd card..then boot into twrp..wipe data and cache..click install and find ur image and click it..the rom will get flashed to ur device..
Sent from my Micromax A110 using XDA Free mobile app
Click to expand...
Click to collapse
By attempting to flash that stock image above, I lost TWRP and now on stock recovery. I can only access bootloader now. Which file should I try to flash via fastboot? That seems to be my only solution.
DocDroid said:
Yes, unlocked bootloader. Motorola Device Manager tells me my phone's current version is "22.21.11.victara_tmo.tmo.en.us" and I was running Lollipop 5.0 before it went beserk yesterday.
I downloaded the image file from http://www.graffixnyc.com/motox.php under the title "Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip."
I honestly don't know what is wrong!!
Click to expand...
Click to collapse
Why did you download it from there rather than from Motorola's official site? I wouldn't feel confident that the images are actually legitimate. Download them from motorola:
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
From that link click Get recovery images here and download them from the official source.
Hi All!
Here is my situation, I have a moto g xt1072 (Jan 2016) which came with a faulty problem, no sound after 5 seconds of been started. I checked everything (Factory reset via recovery), including both speakers, (both working at 7.5 ohms). Do you think a firmware change or a different ROM can help or it's time to let it go?
Base band: M8926_309101.02.03.19R THEA_EMEA_CUST
Kernel: 3.4.42-gef77327 [email protected] #1
System Version: 24.41.34.thea_retes.retesall.en.EU retes
Complation numer: MPB24.65-34
Everything is stock, no changes were made.
Thanks in advance!!!
@lost101
did you look here
http://forum.xda-developers.com/moto-g-lte
sd_shadow said:
did you look here
http://forum.xda-developers.com/moto-g-lte
Click to expand...
Click to collapse
Yep, if you are familliar with this process could you mind writing me a list of steps in order? I'll investigate 1 by 1 later, I've found so much info that's confusing. My phone is unlcock for any cellphone company, but It's not root, it's stock.
I used to install custom ROM's on my old Defy + but I things are very different now for what I'm seening. :S
Fastboot flash the latest full factory firmware image for your model.
mfastboot download: https://www.androidfilehost.com/?fid=24052804347778493
XT1072 Retail Spain Android 6.0 Factory Firmware Image: https://www.androidfilehost.com/?fid=24533103863143791
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219 (See specific fastboot commands below)
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 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
murrayhawk said:
Yep, if you are familliar with this process could you mind writing me a list of steps in order? I'll investigate 1 by 1 later, I've found so much info that's confusing. My phone is unlcock for any cellphone company, but It's not root, it's stock.
I used to install custom ROM's on my old Defy + but I things are very different now for what I'm seening. :S
Click to expand...
Click to collapse
please dont mess up the flash.. because then you're pretty much ****ed.. as far ive seen and read and heard and tried, there will be no fix..
lost101 said:
Fastboot flash the latest full factory firmware image for your model.
mfastboot download: https://www.androidfilehost.com/?fid=24052804347778493
XT1072 Retail Spain Android 6.0 Factory Firmware Image: https://www.androidfilehost.com/?fid=24533103863143791
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219 (See specific fastboot commands below)
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 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
Click to expand...
Click to collapse
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
ora69 said:
please dont mess up the flash.. because then you're pretty much ****ed.. as far ive seen and read and heard and tried, there will be no fix..
Click to expand...
Click to collapse
I don't have anything to lose, this phone is rebooting itselft every 2 minutes.
murrayhawk said:
I don't have anything to lose, this phone is rebooting itselft every 2 minutes.
Click to expand...
Click to collapse
please, if anything gives a fail, post it on the thread! I myself have hard bricked this device, and now im trying to find the testpoint for it, ive already invested hours into this.. and i have no progress!, its worth it to post it on a thread
murrayhawk said:
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
Click to expand...
Click to collapse
The guide I linked to is not about downgrading. Ignore references to Android 4.3 - it still applies to Android 6.0. It sounds like you have not installed the usb drivers for your phone in Windows. This is a prerequisite. These Moto G drivers will also work for your phone:
Moto G USB Drivers (WinXP/7/8/10 32Bit-64Bit)
Test Fastboot is working by typing: fastboot devices
You may also be able to use RSD Lite - but this again will require you have installed USB drivers for your phone.
murrayhawk said:
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
Click to expand...
Click to collapse
my opinion is use RSD lite first, unless there is not a specific firmware file for your carrier/region...
or there is a high rate of flashing failure with the firmware available.
if RSD lite fails, best to post errors from pc and phone here
before try again, if there's not an obvious fix
then try mfastboot.exe
fastboot.exe is generic android, mfastboot.exe is Motorola specific, for moto's unique system.img...
avoid usb 3.0 ports
make sure the firmware downloaded is correct size, verified MD5 is best.
verify drivers are correct when the device is in fastboot mode
I have generic moto instructions in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my KFFOWI using XDA Labs
sd_shadow said:
my opinion is use RSD lite first, unless there is not a specific firmware file for your carrier/region...
or there is a high rate of flashing failure with the firmware available.
if RSD lite fails, best to post errors from pc and phone here
before try again, if there's not an obvious fix
then try mfastboot.exe
fastboot.exe is generic android, mfastboot.exe is Motorola specific, for moto's unique system.img...
avoid usb 3.0 ports
make sure the firmware downloaded is correct size, verified MD5 is best.
verify drivers are correct when the device is in fastboot mode
I have generic moto instructions in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
i think the tip you gave to avoid usb 3.0 ports will really help, didnt realize i was using the usb 3.0 port
Ok, this is what I did so far: (I'm running Windows 7 64b).
1. RSD Lite 6.2.4: Installed
2. Motorola Mobile Drivers Installation 6.4.0: Installed
3. Motorola Device Manager: Installed
1. I started the mobile into the recovery mode
2. Connected the moto cable to the pc
3. Opened RSD Lite, loaded the new firmware and hit start boton
4. The process reached a "please reboot manually...."
5. The phone starts but with the old firmware in it.
More Updates: I ran mfastboot sequence and every command returned OKAY. The issue still remains intact, sound works for 5 seconds, and the firmware has not been updated.
Any thoughts?
murrayhawk said:
More Updates: I ran mfastboot sequence and every command returned OKAY. The issue still remains intact, sound works for 5 seconds, and the firmware has not been updated.
Any thoughts?
Click to expand...
Click to collapse
I want to see a full and complete log of the fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
lost101 said:
I want to see a full and complete log of the fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Ok, please check the attachment.
It looks increasingly like your issue is hardware, not software related. The only remaining software option I can suggest is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
lost101 said:
It looks increasingly like your issue is hardware, not software related. The only remaining software option I can suggest is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
Can you explain why does it retain the original firmware after mfastboot commandas ran well?
Just a quick reminder. This moto g XT1702 Jan2016, is not rooted, bootloader is locked and has everything stock, it came with Android 6.0 installed.
murrayhawk said:
Can you explain why does it retain the original firmware after mfastboot command as ran well?
Click to expand...
Click to collapse
How do you mean original Firmware? You are flashing a Stock Android 6.0 firmware image.
lost101 said:
How do you mean original Firmware? You are flashing a Stock Android 6.0 firmware image.
Click to expand...
Click to collapse
What I have right now is : System Version: 24.41.34.thea_retes.retesall.en.EU retes and after flashing to XT1072_THEA_RETES_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml. I'm still having 24.41.34.thea_retes.retesall.en.EU retes.
Hey guys, for those of you who have bricked your phone by upgrading to Oreo then tried downgrading to nougat, I may have a fix for you. Also news that Android O can be installed on Sprint (and possibly locked bootloader variants too). I'm going to sleep now, I'll post a couple tutorials tomorrow when I get home from work but I wanted to give you guys a little sneak peak of what I've discovered.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: also, this is running buttery smooth for me. Which leads to believe those of you having performance issues with O it's probably due to some carrier apps/features, which would be in the OEM partition. Side note, this is a retail rom, which means no carrier bloat/features. This is as if you were to buy it unlocked straight from Motorola. This also means I have no VoWiFi on Sprint. If anyone could find a way to implement this in O that would be awesome.
Sent from my Moto Z (2) using Tapatalk
already flashed retail O on Sprint and now looking for root solution
HugeUFO said:
already flashed retail O on Sprint and now looking for root solution
Click to expand...
Click to collapse
Did flashing magisk not work?
donjuro said:
Did flashing magisk not work?
Click to expand...
Click to collapse
nope, I never tried Magisk before. And a complete backup needs root access, but to gain root access I need Magisk, which recommends a backup[emoji23]
通过我的 Moto Z (2) 上的 Tapatalk发言
donjuro said:
I'll post a couple tutorials tomorrow
Click to expand...
Click to collapse
Great, looking forward to it.
HugeUFO said:
nope, I never tried Magisk before. And a complete backup needs root access, but to gain root access I need Magisk, which recommends a backup[emoji23]
通过我的 Moto Z (2) 上的 Tapatalk发言
Click to expand...
Click to collapse
You don't need root access to backup with twrp
donjuro said:
You don't need root access to backup with twrp
Click to expand...
Click to collapse
Oh thanks, I will try to flash a twrp to backup.
donjuro Please come back to as if you will find moment. We are still waiting.
Hey guys, sorry I've been gone for so long. Life really kicks your ass sometimes
Anyways, it looks like just about every carrier is on 8.0 now except Sprint, but if you're on another carrier yet you still haven't been upgraded you could try this too.
So basically all you have to do is download NASH_RETAIL_8.0.0_OPX27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from one of these two mirrors.
https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/
https://mirrors.lolinet.com/firmware/moto/nash/official/
Unpackage the zip file, and inside the folder create a flashall.bat, here is what you will put in the bat file
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Save it, put your phone in fastboot mode, run it, and that should be it. You might want to make a backup of any valuable files first though as this WILL erase everything and will start you from scratch!
For those of you wanting to keep your carrier specific features, you can use your carrier specific files from any of these mirrors, but for stability purposes I highly recommend using the RETAIL version.
robdevil said:
donjuro Please come back to as if you will find moment. We are still waiting.
Click to expand...
Click to collapse
what is the issue you are having?
thanks mate, and wanna ask for twrp backup issue, anyone have issue for restore from twrp,
i've got bootloop after TWRP restore, (was working before backup)
once android O stable, I can upgrade to O asap, thanks again
ilovemeow said:
thanks mate, and wanna ask for twrp backup issue, anyone have issue for restore from twrp,
i've got bootloop after TWRP restore, (was working before backup)
once android O stable, I can upgrade to O asap, thanks again
Click to expand...
Click to collapse
If it is just restarting into TWRP over and over, you might just need to switch to a different slot. It is there in the reboot area of TWRP.
JAWheat411 said:
If it is just restarting into TWRP over and over, you might just need to switch to a different slot. It is there in the reboot area of TWRP.
Click to expand...
Click to collapse
hmm, not really restarting into twrp,
i pass the twrp, reboot itself before "hellomoto" screen appear
Are you able to reflash the stock boot image in bootloader?
Help Please.
donjuro said:
Hey guys, for those of you who have bricked your phone by upgrading to Oreo then tried downgrading to nougat, I may have a fix for you. Also news that Android O can be installed on Sprint (and possibly locked bootloader variants too). I'm going to sleep now, I'll post a couple tutorials tomorrow when I get home from work but I wanted to give you guys a little sneak peak of what I've discovered.
Edit: also, this is running buttery smooth for me. Which leads to believe those of you having performance issues with O it's probably due to some carrier apps/features, which would be in the OEM partition. Side note, this is a retail rom, which means no carrier bloat/features. This is as if you were to buy it unlocked straight from Motorola. This also means I have no VoWiFi on Sprint. If anyone could find a way to implement this in O that would be awesome.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
So i have a T-Mobile variant and I attempted to root and got a bootloop. SO i surfed the web and found this. Downloaded firmware from the 3nd site you linked, did everything else as well and I don't have wifi or mobile data. Please help
AsapJuno said:
So i have a T-Mobile variant and I attempted to root and got a bootloop. SO i surfed the web and found this. Downloaded firmware from the 3nd site you linked, did everything else as well and I don't have wifi or mobile data. Please help
Click to expand...
Click to collapse
What version does your baseband say?
Sent from my Moto Z (2) using Tapatalk
donjuro said:
What version does your baseband say?
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It says unknown now
AsapJuno said:
It says unknown now
Click to expand...
Click to collapse
Well, you're kind of in for a bad time now... The "official" tmobile oreo zip that's out there flashes fine but then you end up with no baseband.
@MootNewt made a zip here: https://forum.xda-developers.com/z2-force/help/t-mobile-oreo-flashall-t3755086/post75810018
that will flash to the latest tmobile oreo (with feb update) but you'll end up not passing safetynet, even with Magisk.
You will have root via Magisk, though, so there's that.
This is where I am right now. :/
AsapJuno said:
It says unknown now
Click to expand...
Click to collapse
Also if it helps here is a T-Mobile flash all to the latest firmware. https://drive.google.com/file/d/153BdClEOK3ZzpgiM37Ti4Y8lkyXPcz0S/view?usp=sharing
Just run the flash all bat file while your phone is in bootloader mode. This will wipe everything, just a fair warning. I am using this now. No problems with safety net here.
JAWheat411 said:
Also if it helps here is a T-Mobile flash all to the latest firmware. https://drive.google.com/file/d/153BdClEOK3ZzpgiM37Ti4Y8lkyXPcz0S/view?usp=sharing
Just run the flash all bat file while your phone is in bootloader mode. This will wipe everything, just a fair warning. I am using this now. No problems with safety net here.
Click to expand...
Click to collapse
Are you saying that it's got the 27.1 update and it passes safetynet?
e: AND it doesn't eat your baseband?