Moto X4 1900-6 Bricked - Moto X4 Questions & Answers

Please, someone help me, i just updated the system from menu today and now my phone dont boot
I just receive this msg:
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-Through from normal boot mode
Click to expand...
Click to collapse
When i try to reinstall the system, i get this:
C:\Users\Casa\Desktop\platform-tools>fastboot flash boot twrp-3.2.3-1-payton.img
Sending 'boot' (30184 KB) OKAY [ 0.991s]
Writing 'boot' (bootloader) Invalid partitio
n name boot
FAILED (remote failure)
Finished. Total time: 1.016s
Click to expand...
Click to collapse
Need my phone back

You didn't provide any details of what ROM you were on, but if you were on LOS15.1 you will find your answer only be reading the last couple of pages in the ROM thread.
Note from developer:
erfanoabdi said:
Guys I'm really sorry about OTA
It bricks device but to unbrick it just do this in bootloader node
fastboot --set-active=b
OTAs will be fixed after next update
Which means, need to manually install next update with TWRP then, OTA after that
Sorry again
Click to expand...
Click to collapse

Variant? Bootloader unlocked? Custom ROM?
???
lol

Neffy27 said:
Variant? Bootloader unlocked? Custom ROM?
???
lol
Click to expand...
Click to collapse
its last lineage 15.1 update, bootloader unlocked

LucasCajado said:
its last lineage 15.1 update, bootloader unlocked
Click to expand...
Click to collapse
Did you read my post? There is a thread dedicated to this release. You should be reading and posting there (emphasis on reading). No reason to create a separate thread.

jhedfors said:
Did you read my post? There is a thread dedicated to this release. You should be reading and posting there (emphasis on reading). No reason to create a separate thread.
Click to expand...
Click to collapse
It would be very nice and helpful of you and probably save you some time writing the same post repeatedly if you would just provide a link to the thead you are referencing.

reedc83 said:
It would be very nice and helpful of you and probably save you some time writing the same post repeatedly if you would just provide a link to the thead you are referencing.
Click to expand...
Click to collapse
LOL
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265

Related

Lollipop 5.1

I managed to compile Lollipop 5.1 for this phone, but when I attempt to flash it it gives me the following errors:
Code:
fastboot flash system system.img
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.004s
Same thing with userdata
Code:
fastboot flash userdata userdata.img
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.005s
Any help will be appreciated!
jdmedeiros said:
I managed to compile Lollipop 5.1 for this phone, but when I attempt to flash it it gives me the following errors:
Code:
fastboot flash system system.img
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.004s
Same thing with userdata
Code:
fastboot flash userdata userdata.img
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.005s
Any help will be appreciated!
Click to expand...
Click to collapse
Try to use htc_fastboot or make flashable .zip
you are bootloader unlocked correct? and as the above post said,try with the fastboot binary from htc or replace a current rom /system folder in a zip with yours,then try flashing it through a recovery (just make sure to change the manifest to include/not include any apks/libs you have)
Would you believe that htc_fastboot did the job? I never expected it to work, but it did. The phone won't boot... but that's another problem. I used a pre-built kernel instead of building it; maybe it has to do with that, or maybe I need a specific 5.x kernel, but the latest on the htcdev site is for 4.x Any tips would be appreciated.
pattyboi:) said:
you are bootloader unlocked correct? and as the above post said,try with the fastboot binary from htc or replace a current rom /system folder in a zip with yours,then try flashing it through a recovery (just make sure to change the manifest to include/not include any apks/libs you have)
Click to expand...
Click to collapse
jdmedeiros said:
Would you believe that htc_fastboot did the job? I never expected it to work, but it did. The phone won't boot... but that's another problem. I used a pre-built kernel instead of building it; maybe it has to do with that, or maybe I need a specific 5.x kernel, but the latest on the htcdev site is for 4.x Any tips would be appreciated.
Click to expand...
Click to collapse
your gonna need to compile one with the updated framebuffer from rbheromax's repo,or i can compile one for you once i get my phone up
pattyboi:) said:
your gonna need to compile one with the updated framebuffer from rbheromax's repo,or i can compile one for you once i get my phone up
Click to expand...
Click to collapse
I'll compile one right now, i got my source ready
---------- Post added at 03:21 AM ---------- Previous post was at 02:51 AM ----------
http://tempsend.com/8D78C9A3A0
compiled with f2fs (which i believe is needed), lcd kcal, and framebuffer from cm kernel
replace with kernel in device tree and run "make bootimage"
fastboot that boot.img and test
kernel works
boots cm12 from a5
snappy, gonna seek out all the bugs now
Thanks guys, I still have a few edges to iron out and very little free time. By the way I built AOSP 5.1 and not CM
pattyboi:) said:
your gonna need to compile one with the updated framebuffer from rbheromax's repo,or i can compile one for you once i get my phone up
Click to expand...
Click to collapse
rbheromax said:
I'll compile one right now, i got my source ready
---------- Post added at 03:21 AM ---------- Previous post was at 02:51 AM ----------
http://tempsend.com/8D78C9A3A0
compiled with f2fs (which i believe is needed), lcd kcal, and framebuffer from cm kernel
replace with kernel in device tree and run "make bootimage"
fastboot that boot.img and test
Click to expand...
Click to collapse
jdmedeiros said:
Thanks guys, I still have a few edges to iron out and very little free time. By the way I built AOSP 5.1 and not CM
Click to expand...
Click to collapse
I'd love to use an AOSP 5+ rom... Any chance of a build for 64-bit?
Sent from my HTC_0PCV2 using XDA Free mobile app
Any progress on this?
Does this ROM have any issues so far? I did all the rooting and unlocking on his desire 510 and keeps asking when someone is going to develop a lollipop rom for his 510 -_-
He's one of those guys.
So what happened to lollipop? I was really excited for this.
rbheromax said:
I'll compile one right now, i got my source ready
---------- Post added at 03:21 AM ---------- Previous post was at 02:51 AM ----------
http://tempsend.com/8D78C9A3A0
compiled with f2fs (which i believe is needed), lcd kcal, and framebuffer from cm kernel
replace with kernel in device tree and run "make bootimage"
fastboot that boot.img and test
Click to expand...
Click to collapse
Hey would you mind sending me the kernel, i'd would also like to boot up into lollipop
Im working on 5.1.1 myself. Hopefully going to have something going soon
I cant wait . hurry
OnlySomeDood said:
Im working on 5.1.1 myself. Hopefully going to have something going soon
Click to expand...
Click to collapse
hope you made it good rom . poor hts 510 dont have not much rom . so far

[Q] [q] please help me!!!

I have a moto x xt1053 , factory unlocked version bought from moto maker.
previously i had unlocked bootloader, rooted my phone and done all sorts of **** with it like flashing cm12, but since i heard lollipop was officially coming, i decided to revert to stock. i returned to 4.2.2 by manually flashing it via mfastboot.
All though a few things had a remote failure while flashing, it worked well. now i had a stock moto x with unlocked bootloader. when i repeatedly received notifications from moto to update to kitkat, i accepted. it downloaded and when it went to that android logo with exclamation, i by mistake held the volume up and power button for a few seconds which made it reboot during the update. now, the phone doesn't work. it only opens to fastboot and it says my device is locked
although i had an unlocked bootloader.
now the device only says a few things like -
downgraded security version
update gpt_main version failed
failed to hab check
CID read failure
invalid cid status 0*69
customer id error contact dealer ; 0xdead
No SP partition found
fastboot reason; invalid cid
i have tried everything to save it. nothing works. i cant flash images because on rsd lite it always fails, and manually it says bootloader permission denied since the bootloader has got locked. even TWRP won't flash.what do i do?
When i try to click on anything such as recovery or factory or barcode or bp tools, it says boot up failed and load kernel ((boot) failed in red.
PLEASE HELP ME FIX MY PHONE XDA!! i need you all!! i don't mind losing data or anything. i dont even mind running cm forever, but please get it to work!!
thanks a lot in advance.
You missed all the warnings to NOT DOWNGRADE and went back to 4.2.2.
See -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
Determine the bootloader version on your phone. What is it?
If it is 30.B7 or lower, grab the 4.4.4 image/sbf file for your phone, and flash it by following the Requirements and Option 5 from Post #2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
If your bootloader is 30.BC or higher, or you had 5.1 on your phone, you best bet is to wait for a 5.1 SBF for your phone to be leaked or posted. There are some possibilities but they depend on finding the correct leaked Lollipop OTA zip file for your phone.
KidJoe said:
You missed all the warnings to NOT DOWNGRADE and went back to 4.2.2.
See -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
Determine the bootloader version on your phone. What is it?
If it is 30.B7 or lower, grab the 4.4.4 image/sbf file for your phone, and flash it by following the Requirements and Option 5 from Post #2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
If your bootloader is 30.BC or higher, or you had 5.1 on your phone, you best bet is to wait for a 5.1 SBF for your phone to be leaked or posted. There are some possibilities but they depend on finding the correct leaked Lollipop OTA zip file for your phone.
Click to expand...
Click to collapse
i have tried doing what you asked me to do. when i try to flash it manually from mfastboot, the first few things don't get flashed at all and later on during the flashing of system and stuff, it fails because bootloader access is denied.
please help me! im in deep trouble..:crying:
my bootloader version is 30.B7(*)
thanks a lot mark venture! youre the best!
i tried flashing lots of things like all kitkats factory images but it wont flash
suryanshsanghvi said:
i have tried doing what you asked me to do. when i try to flash it manually from mfastboot, the first few things don't get flashed at all and later on during the flashing of system and stuff, it fails because bootloader access is denied.
please help me! im in deep trouble..:crying:
my bootloader version is 30.B7(*)
thanks a lot mark venture! youre the best!
i tried flashing lots of things like all kitkats factory images but it wont flash
Click to expand...
Click to collapse
First... STOP FLASHING "all kitkats factory images"... that is how you got your self in this situation.
There are warnings about downgrading (flashing older SBFs) because its often either difficult and in many cases not possible to recover when you've bricked because of it.
Next... What Model X do you have, and who is the carrier?
KidJoe said:
First... STOP FLASHING "all kitkats factory images"... that is how you got your self in this situation.
There are warnings about downgrading (flashing older SBFs) because its often either difficult and in many cases not possible to recover when you've bricked because of it.
Next... What Model X do you have, and who is the carrier?
Click to expand...
Click to collapse
I have a moto x gen1 bought from moto maker. It's is factory unlocked gsm an:cyclops: came with TMO SIM card. Please, help me.
suryanshsanghvi said:
I have a moto x gen1 bought from moto maker. It's is factory unlocked gsm an:cyclops: came with TMO SIM card. Please, help me.
Click to expand...
Click to collapse
Have you ever tried any of the Lollipop leaks? either 5.02 or 5.1? Did your phone get prompted to update to Lollipop and fail?
IF your bootloader is still 30.B7, and you have NOT tried flashing anything but XT1053 "retail" roms, and have NOT flashed the leaked 5.02 or now 5.1 or the offical 5.1, then... hit Moto's web site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and request access then download "MOTO X, GSM Dev Edition:
KK-4.4.4-KXA21.12-L1.29.1-2 (Retail) MR4"
Or download this copy from file factory which is the same rom version -> http://www.filefactory.com/file/2yh...4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip
Next hit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and view post #2... Use the requirements and Option #5 with this downloaded file, EXACTLY as written! Do NOT skip any steps.
If it errors, copy/paste exactly what it says on the PC, or take a picture of the phone's screen and post it.
Further, if this fails each time it tries to flash GPT.BIN, then you may be stuck until a 5.1 SBF leaks and you can flash with that as any option risks bricking your phone even worse.
KidJoe said:
Have you ever tried any of the Lollipop leaks? either 5.02 or 5.1? Did your phone get prompted to update to Lollipop and fail?
IF your bootloader is still 30.B7, and you have NOT tried flashing anything but XT1053 "retail" roms, and have NOT flashed the leaked 5.02 or now 5.1 or the offical 5.1, then... hit Moto's web site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and request access then download "MOTO X, GSM Dev Edition:
KK-4.4.4-KXA21.12-L1.29.1-2 (Retail) MR4"
Or download this copy from file factory which is the same rom version -> http://www.filefactory.com/file/2yh...4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip
Next hit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and view post #2... Use the requirements and Option #5 with this downloaded file, EXACTLY as written! Do NOT skip any steps.
If it errors, copy/paste exactly what it says on the PC, or take a picture of the phone's screen and post it.
Further, if this fails each time it tries to flash GPT.BIN, then you may be stuck until a 5.1 SBF leaks and you can flash with that as any option risks bricking your phone even worse.
Click to expand...
Click to collapse
What do I do if I've tried flashing 5.0.2 leaked rom of xt1058 before? It did work at that time though. So now do I have to wait till moto updates their website and puts up 5.1 for my phone on the site? I went to the service centre today and they told me to shell out 300$ for repairs. I could buy a new phone with that cash. Really need all you dev's help.
suryanshsanghvi said:
What do I do if I've tried flashing 5.0.2 leaked rom of xt1058 before? It did work at that time though. So now do I have to wait till moto updates their website and puts up 5.1 for my phone on the site? I went to the service centre today and they told me to shell out 300$ for repairs. I could buy a new phone with that cash. Really need all you dev's help.
Click to expand...
Click to collapse
As i said before, DOWNGRADING is what got you into this situation. You can't do that. There are many warnings. Even a link to a thread discussing it (which also has links to many who have attempted to downgrade and have bricked).
If you had 5.x on there, and try to flash 4.x on there then you are downgrading.. NOW, the one caveat being IF you restored one of the TWRP backups of 5.x onto your phone, as that usually only restored /system and NOTHING ELSE which is better.. Its the OTHER PARTS that get in the way and cause issues when trying to downgrade.
IF however you flashed the XT1058 ROM (using RSDLite or fastboot), then took one of the LEAKED 5.x OTA updates at some point, its a different matter.
Again, *IF* your bootloader is 30.B7, then you should be able to do what I said a few posts ago. There is a 70% chance it will fix you. If not, then yes we must wait for a 5.1 SBF file for your carrier/model. Since you have the XT1053, Moto will eventually post it on their web site where they put Developer Edition recovery images, and you don't have to rely on a 5.1 SBF to LEAK (since leaks are not official, you cant count on them appearing)
IF your bootloader is 30.BC, 30.BD, or 30.BE, there are posts of people extracting the GPT.BIN and Bootloader from the leaked OTA zip files and flashing them to get their phone working, HOWEVER see this one -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-bricked-device-t3076918 where after doing that, getting it working, he took an OTA and it bricked him even worse.. That is why I say the SAFEST way would be to wait until the 5.1 SBF comes.. IF you want to attempt this, I won't advise you as to how, and will say that if you figure it out, DO NOT take an OTA!! Instead wait until the 5.1 SBF is posted, then fully flash that.
KidJoe said:
As i said before, DOWNGRADING is what got you into this situation. You can't do that. There are many warnings. Even a link to a thread discussing it (which also has links to many who have attempted to downgrade and have bricked).
If you had 5.x on there, and try to flash 4.x on there then you are downgrading.. NOW, the one caveat being IF you restored one of the TWRP backups of 5.x onto your phone, as that usually only restored /system and NOTHING ELSE which is better.. Its the OTHER PARTS that get in the way and cause issues when trying to downgrade.
IF however you flashed the XT1058 ROM (using RSDLite or fastboot), then took one of the LEAKED 5.x OTA updates at some point, its a different matter.
Again, *IF* your bootloader is 30.B7, then you should be able to do what I said a few posts ago. There is a 70% chance it will fix you. If not, then yes we must wait for a 5.1 SBF file for your carrier/model. Since you have the XT1053, Moto will eventually post it on their web site where they put Developer Edition recovery images, and you don't have to rely on a 5.1 SBF to LEAK (since leaks are not official, you cant count on them appearing)
IF your bootloader is 30.BC, 30.BD, or 30.BE, there are posts of people extracting the GPT.BIN and Bootloader from the leaked OTA zip files and flashing them to get their phone working, HOWEVER see this one -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-bricked-device-t3076918 where after doing that, getting it working, he took an OTA and it bricked him even worse.. That is why I say the SAFEST way would be to wait until the 5.1 SBF comes.. IF you want to attempt this, I won't advise you as to how, and will say that if you figure it out, DO NOT take an OTA!! Instead wait until the 5.1 SBF is posted, then fully flash that.
Click to expand...
Click to collapse
I'm pretty sure the BSF will be put up by 2 weeks so I'll just wait till then. But when I get it, how will I flash it? RSD lite right? Cause if I do it manually through mfastboot, stuff doesn't get flashed cause boot loader is locked. If it wasn't locked, I'd flash twrp days back.
KidJoe said:
As i said before, DOWNGRADING is what got you into this situation. You can't do that. There are many warnings. Even a link to a thread discussing it (which also has links to many who have attempted to downgrade and have bricked).
If you had 5.x on there, and try to flash 4.x on there then you are downgrading.. NOW, the one caveat being IF you restored one of the TWRP backups of 5.x onto your phone, as that usually only restored /system and NOTHING ELSE which is better.. Its the OTHER PARTS that get in the way and cause issues when trying to downgrade.
IF however you flashed the XT1058 ROM (using RSDLite or fastboot), then took one of the LEAKED 5.x OTA updates at some point, its a different matter.
Again, *IF* your bootloader is 30.B7, then you should be able to do what I said a few posts ago. There is a 70% chance it will fix you. If not, then yes we must wait for a 5.1 SBF file for your carrier/model. Since you have the XT1053, Moto will eventually post it on their web site where they put Developer Edition recovery images, and you don't have to rely on a 5.1 SBF to LEAK (since leaks are not official, you cant count on them appearing)
IF your bootloader is 30.BC, 30.BD, or 30.BE, there are posts of people extracting the GPT.BIN and Bootloader from the leaked OTA zip files and flashing them to get their phone working, HOWEVER see this one -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-bricked-device-t3076918 where after doing that, getting it working, he took an OTA and it bricked him even worse.. That is why I say the SAFEST way would be to wait until the 5.1 SBF comes.. IF you want to attempt this, I won't advise you as to how, and will say that if you figure it out, DO NOT take an OTA!! Instead wait until the 5.1 SBF is posted, then fully flash that.
Click to expand...
Click to collapse
@KidJoe - props for helping this guy out man!
Sent from my XT1053 using Tapatalk
suryanshsanghvi said:
I'm pretty sure the BSF will be put up by 2 weeks so I'll just wait till then. But when I get it, how will I flash it? RSD lite right? Cause if I do it manually through mfastboot, stuff doesn't get flashed cause boot loader is locked. If it wasn't locked, I'd flash twrp days back.
Click to expand...
Click to collapse
There is no time table for when Moto will post the SBF file to their web site. We can hope they will do it sooner, rather than later. But at least with the XT1053, you know Moto WILL post it, unlike those who rely on leaks.
No. Do not RSDLite. RSDLite will likely fail due to the GPT errors. Again, use Option 5 of that post and mfastboot EXACTLY as written.
As long as you are flashing the Stock, and digitally signed by Moto rom for that phone carrier/model, you can flash with a locked bootloader. Its when you try to flash the rom for another model/carrier that locked bootloader comes into play.
KidJoe said:
There is no time table for when Moto will post the SBF file to their web site. We can hope they will do it sooner, rather than later. But at least with the XT1053, you know Moto WILL post it, unlike those who rely on leaks.
No. Do not RSDLite. RSDLite will likely fail due to the GPT errors. Again, use Option 5 of that post and mfastboot EXACTLY as written.
As long as you are flashing the Stock, and digitally signed by Moto rom for that phone carrier/model, you can flash with a locked bootloader. Its when you try to flash the rom for another model/carrier that locked bootloader comes into play.
Click to expand...
Click to collapse
Bro you're the best.thanks a lot man!
Official ROM image from MOTO
KidJoe said:
hit Moto's web site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and request access then download "MOTO X, GSM Dev Edition:
KK-4.4.4-KXA21.12-L1.29.1-2 (Retail) MR4"
Or download this copy from file factory which is the same rom version -> http://www.filefactory.com/file/2yh...4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip
.
Click to expand...
Click to collapse
Filefactory is dead-slow. Moto took a long time to give me access to the factory roms. I am linking 4.4.4 here for the community's convenience.
https://drive.google.com/open?id=0B1KTBUtop5_HZkxNS2NZdkdQZW8&authuser=0
XT1053_4.4.4_213.44.1 (KXA21.12-L1.29.1_2_cid9_CFC_1FF)
md5 = 22773e5981cb04f6286a12e9488d0db5
sha1 = f8e0d2c0e04c2414f16a44c21ddb0ca18b2122e4
KidJoe said:
There is no time table for when Moto will post the SBF file to their web site. We can hope they will do it sooner, rather than later. But at least with the XT1053, you know Moto WILL post it, unlike those who rely on leaks.
No. Do not RSDLite. RSDLite will likely fail due to the GPT errors. Again, use Option 5 of that post and mfastboot EXACTLY as written.
As long as you are flashing the Stock, and digitally signed by Moto rom for that phone carrier/model, you can flash with a locked bootloader. Its when you try to flash the rom for another model/carrier that locked bootloader comes into play.
Click to expand...
Click to collapse
I can't wait longer. Please tell me an alternate way to fix my phone? Or a leaked file for USA unlocked phone xt1053 of 5.1
As soon as it works, I'll switch to cyanogenmod and never switch back again.
Can you please tell me which moto boot gpt and recovery to flash from which sbf files so it boots up and I'll install twrp. I'll take the risk cause my phone's already ****ed up. If it's dead, it's dead. It'll be last attempt. You need not worry. Please tell me.
suryanshsanghvi said:
I can't wait longer. Please tell me an alternate way to fix my phone? Or a leaked file for USA unlocked phone xt1053 of 5.1
As soon as it works, I'll switch to cyanogenmod and never switch back again.
Can you please tell me which moto boot gpt and recovery to flash from which sbf files so it boots up and I'll install twrp. I'll take the risk cause my phone's already ****ed up. If it's dead, it's dead. It'll be last attempt. You need not worry. Please tell me.
Click to expand...
Click to collapse
You said your bootloader was 30.B7, but you have NOT yet said if you tried what I put in Post #6....
Did you try that? what happened? I had asked you to copy/paste any errors and I didn't see them.
new error
KidJoe said:
You said your bootloader was 30.B7, but you have NOT yet said if you tried what I put in Post #6....
Did you try that? what happened? I had asked you to copy/paste any errors and I didn't see them.
Click to expand...
Click to collapse
till now it just said-
downgraded security version
update gpt_main version failed
failed to hab check
CID read failure
invalid cid status 0*69
customer id error contact dealer ; 0xdead
No SP partition found
fastboot reason; invalid cid
but now it says-
downgraded security version
update gpt_main version failed
failed to hab check for gpt _backup:0x35
CID read failure
invalid cid status 0*69
customer id error contact dealer ; 0xdead
No SP partition found
fastboot reason; invalid cid
:crying:
i tried flashing official sbf using the method you told me to use. this is the result
KidJoe said:
You said your bootloader was 30.B7, but you have NOT yet said if you tried what I put in Post #6....
Did you try that? what happened? I had asked you to copy/paste any errors and I didn't see them.
Click to expand...
Click to collapse
on command prompt, the followin takes place-
C:\Users\user\Desktop\moto x\platform-tools>mfastboot getvar max-download-size
max-download-size: 805306368
finished. total time: 0.149s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.301s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.223s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash motoboot motoboot.im
g
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.421s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.703s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.004s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.290s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.212s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash motoboot motoboot.im
g
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.426s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.708s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash logo logo.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (628 KB)...
OKAY [ 0.383s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.485s
C:\Users\user\Desktop\moto x\platform-tools>
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash boot boot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.986s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.088s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash recovery recovery.im
g
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.106s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 896527596 bytes
error: cannot load 'system.img': Not enough space
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.767s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 3.889s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.102s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.099s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'fsg' (1223 KB)...
OKAY [ 0.426s]
writing 'fsg'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.529s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.104s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot reboot
rebooting...
finished. total time: 0.002s
PLEASEE HELPPP
At this point, you need to wait on the 5.1 SBF to be safe. Anything else could risk bricking you even worse than you are, so I don't want to suggest it.
Keep an eye on -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 and see if it pops up there before Moto posts it..
Or maybe @s5610 has an idea?
KidJoe said:
At this point, you need to wait on the 5.1 SBF to be safe. Anything else could risk bricking you even worse than you are, so I don't want to suggest it.
Keep an eye on -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 and see if it pops up there before Moto posts it..
Or maybe @s5610 has an idea?
Click to expand...
Click to collapse
Can you give me link for a proper mfastboot. Mine says could not allocate and stuff while writing system
suryanshsanghvi said:
Can you give me link for a proper mfastboot. Mine says could not allocate and stuff while writing system
Click to expand...
Click to collapse
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip its the same mfastboot packaged in the 4.4.2 and 4.4.4 roms on moto's web site.

[HELP] Moto X XT1058 AT&T fully bricked! I can't do anything!

So, as the title says, I had a Moto X XT1058 from AT&T.
I updated a long time ago to Lollipop and the phone worked perfectly fine until yesterday, when suddenly shutted down and when I restarted, got stuck on M logo.
I restarted to bootloader(?) pressing power off and vol down buttons.
The version that shows me is 30.BE
The device wasn't unlocked or rooted, because I was happy with the stock ROM, so it says Device is LOCKED ans Status Code 0.
I tried every option on this menu and everyone says (in red):
"No valid PIV block in SP for system
piv validation failed (system)
Boot up failed"
I tryed with abd, fastboot, mfastboot and RSDLite to flash gpt.bin and motoboot.img and every time I do it I get a error, and the operation fails.
For what I've read in tooooooo many posts, it's probably death, but I resist to this idea, so I came here to ask for advice.
THE PHONE IS NOT IN WARRANTY ANY MORE.
Thanks in advance and sorry for my english (not my native language).
why dont you try twrp recovery ?
just flash it
fadyrox said:
why dont you try twrp recovery ?
just flash it
Click to expand...
Click to collapse
Can I do it if my phone isn't rooted? The bootloader it's locked!
Flash full stock att 5.1 rom, it will be fine.
Salik Iqbal said:
Flash full stock att 5.1 rom, it will be fine.
Click to expand...
Click to collapse
Flashing via fastboot mode will be okay !
do search here you will get details !
fadyrox said:
Flashing via fastboot mode will be okay !
do search here you will get details !
Click to expand...
Click to collapse
But I never flashed any ROM on this phone. I got Lollipop from a OTA update. My phone was stock. Never rooted, never unlock bootloader. I didn't find any tutorial to do it with this characteristics.
And it's an AT&T xt1058
MatiCepe said:
But I never flashed any ROM on this phone. I got Lollipop from a OTA update. My phone was stock. Never rooted, never unlock bootloader. I didn't find any tutorial to do it with this characteristics.
And it's an AT&T xt1058
Click to expand...
Click to collapse
first you need to unlock your bootloader .. otherwise you wont be able to recover your device
Please do a search regarding unlocking bootloader !
fadyrox said:
first you need to unlock your bootloader .. otherwise you wont be able to recover your device
Please do a search regarding unlocking bootloader !
Click to expand...
Click to collapse
The bootloader of the XT1058 from AT&T is'nt unlockable.... That's the big trouble. I've read that it can be done if it's no 4.2.2, but not if the version is newer.
MatiCepe said:
The bootloader of the XT1058 from AT&T is'nt unlockable.... That's the big trouble. I've read that it can be done if it's no 4.2.2, but not if the version is newer.
Click to expand...
Click to collapse
Download rsd lite for windows, get latest stock rom for att, reboot your phone into fastboot, flash stock rom and you are done.
Salik Iqbal said:
Download rsd lite for windows, get latest stock rom for att, reboot your phone into fastboot, flash stock rom and you are done.
Click to expand...
Click to collapse
I searched and the lastone is ATT_XT1058_5.1.0_LPA23.12-21.7_cid1_CFC.xml.zip. I try to flash it on my phone via RSD and the process showsme this error:
Failed flashing process. 4/18 flash motoboot "motoboot.img" -> Phone returned FAIL.
MatiCepe said:
I searched and the lastone is ATT_XT1058_5.1.0_LPA23.12-21.7_cid1_CFC.xml.zip. I try to flash it on my phone via RSD and the process showsme this error:
Failed flashing process. 4/18 flash motoboot "motoboot.img" -> Phone returned FAIL.
Click to expand...
Click to collapse
Is your phone is charge enough? Search 5.1.1 att xml zip
can anybody give a solution for this problem because i am also with a xt1058 at&t, The device wasn't unlocked or rooted and the version that shows me is 30.BE too
sorry my english
What's up with your device any screen shot?
Hi, i have the same problem, my device is locked by AT&T and i cant flash the firmware< i have a unlock code from the AT&T company, how I can introdce that code manually? Thanks!
Thank you
H3c4rtr1 said:
Hi, i have the same problem, my device is locked by AT&T and i cant flash the firmware< i have a unlock code from the AT&T company, how I can introdce that code manually? Thanks!
Click to expand...
Click to collapse
You can help how you got the code, give details.
Thank you

Issue with updating

Hello,
I need support here I purchased my phone from eBay and the seller changed the language and install play Store for me ,now I tried to update the device to last firmware but its give me no update available .
I look into these issue and downloaded the firmware manually give another message that Can't verify update
So please if any one can help me here thanks
didmytime said:
Hello,
I need support here I purchased my phone from eBay and the seller changed the language and install play Store for me ,now I tried to update the device to last firmware but its give me no update available .
I look into these issue and downloaded the firmware manually give another message that Can't verify update
So please if any one can help me here thanks
Click to expand...
Click to collapse
how you updating.
Boot loader is unlocked out of the box probably that's why you can't update.
didmytime said:
Hello,
I need support here I purchased my phone from eBay and the seller changed the language and install play Store for me ,now I tried to update the device to last firmware but its give me no update available .
I look into these issue and downloaded the firmware manually give another message that Can't verify update
So please if any one can help me here thanks
Click to expand...
Click to collapse
What software version are you using?
riz157 said:
how you updating.
Boot loader is unlocked out of the box probably that's why you can't update.
Click to expand...
Click to collapse
So how can I fix that ?
whatwhat1 said:
What software version are you using?
Click to expand...
Click to collapse
8.0.7.0.0
didmytime said:
8.0.7.0.0
Click to expand...
Click to collapse
Same version as me. You have a vendor ROM and not the official ROM installed on your phone. I don't know how to check if the bootloader is locked/unlocked.
I've got 8.0.10.0 (mahcndi)
What does that mean?
What's the difference between vendor Rom & official Rom?
whatwhat1 said:
......I don't know how to check if the bootloader is locked/unlocked.
Click to expand...
Click to collapse
Check out this post:
http://en.miui.com/thread-279195-1-1.html
Forgive me for my noobiness here but now I am worried. If I have the 8.0.7.0 mahcndi does this mean I will not get the official updates or any updates at all? When it's an official rom do they still come ota even if I'm in Canada for example.
Thanks in advance
imapfsr said:
Forgive me for my noobiness here but now I am worried. If I have the 8.0.7.0 mahcndi does this mean I will not get the official updates or any updates at all? When it's an official rom do they still come ota even if I'm in Canada for example.
Thanks in advance
Click to expand...
Click to collapse
Do you have 8.0.7.0 or 8.0.7.0.0? If you have the latter one, then you will not get updates.
whatwhat1 said:
Do you have 8.0.7.0 or 8.0.7.0.0? If you have the latter one, then you will not get updates.
Click to expand...
Click to collapse
Thanks whatwhat,
So it seems I have the double 0 so that sucks. Do you mind if I ask what I need to do to get this phone on a version that will give me the updates when they are available. Again, any direction you can provide me would be greatly appreciated.
imapfsr said:
Thanks whatwhat,
So it seems I have the double 0 so that sucks. Do you mind if I ask what I need to do to get this phone on a version that will give me the updates when they are available. Again, any direction you can provide me would be greatly appreciated.
Click to expand...
Click to collapse
You can check if your bootloader is locked or unlocked and that may be preventing it from updating. http://en.miui.com/thread-279195-1-1.html
But you really need to flash the official MIUI ROM to keep things updated.
Shouldn't there be updated versions of these multi-language ROMs we can get and update through the built in updater?
Sent from my Xiaomi Mi Mix using XDA Labs
SWBgHz said:
Shouldn't there be updated versions of these multi-language ROMs we can get and update through the built in updater?
Sent from my Xiaomi Mi Mix using XDA Labs
Click to expand...
Click to collapse
I highly doubt it. Any custom ROM has the same behavior.
I'm in the same situation and am looking for some much needed help: I purchased the Mi Mix and have 8.0.7.0.0 installed. This is all new to me, but this forum has been very helpful, and as I understand this is a vendor ROM and as such I will not be able to get OTA updates. That indeed sucks.
I'm trying to find out what I need to do to my phone on a version that will allow me to receive updates in the future. I've read posts about checking if my bootloader is locked or unlocked, but as I said a lot of that is over my head. Does anyone have some advice, "101" type help that they can provide?
Can I simply download the Stable ROM 8.0.8.0 (or even 8.0.12.0), copy to my phone, run MIUI8 and select the update package?
Surely its not that easy?
ADB, Fastboot, etc.. its all new to me. I would appreciate any assistance. Thanks!
Unlocked bootloader won't stop updates just vendor rom. you are right it's not that easy follow the guides in the guide section.
still stuck on 8.0.7.0.0 and this is what adb tells me:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.055s]
finished. total time: 0.057s
Thats greek to me.
Is that good / bad?
Can anyone point me to a specific URL with step by step instructions to get this off the vendor rom and onto something updatable?
TIA
favsob said:
still stuck on 8.0.7.0.0 and this is what adb tells me:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.055s]
finished. total time: 0.057s
Thats greek to me.
Is that good / bad?
Can anyone point me to a specific URL with step by step instructions to get this off the vendor rom and onto something updatable?
TIA
Click to expand...
Click to collapse
your device is already unlocked. go to the thread with step by step instructions on how to flash any rom you want and load TWRP.
https://forum.xda-developers.com/mi-mix/how-to/guide-flash-global-china-rom-root-gapps-t3510592

Root on global rom and custom recovery?

Hi there.
Anyone successfully root and do custom recovery things on the red magic nx609j global rom 8.1.x oreo?
I know in chinese rom. we can do that, but for global rom i still have no luck...
Thanks in advance.
ianseer said:
Hi there.
Anyone successfully root and do custom recovery things on the red magic nx609j?
I know in chinese rom. we can do that, but for global rom i still have no luck...
Thanks in advance.
Click to expand...
Click to collapse
Do you have pie international update?
methuselah said:
Do you have pie international update?
Click to expand...
Click to collapse
Nope, im using v1.14 now
Is the pie already released?
ianseer said:
Nope, im using v1.14 now
Is the pie already released?
Click to expand...
Click to collapse
I am on the same build. Well there is no official international pie but only Chinese and TWRP don't work as I said earlier too that the kernel hasn't been updated to pie. So it creates issues.
So there is no TWRP for pie.
methuselah said:
I am on the same build. Well there is no official international pie but only Chinese and TWRP don't work as I said earlier too that the kernel hasn't been updated to pie. So it creates issues.
So there is no TWRP for pie.
Click to expand...
Click to collapse
No... What i mean is the root and custom recovery method for global rom 8.1 (oreo) . Not for the pie rom. sorry for the confusion... ?
ianseer said:
No... What i mean is the root and custom recovery method for global rom 8.1 (oreo) . Not for the pie rom. sorry for the confusion... ?
Click to expand...
Click to collapse
I don't know about pie flashable zip from here but yeah Omni works without fingerprints
I think he means how root official international Oreo rom!
strakell said:
I think he means how root official international Oreo rom!
Click to expand...
Click to collapse
um,,, yep u're right
I don't know, CMIIW, I already search the forum.... no one do that till now... so the oreo rom is unrootable then?
it feels like "they" dump us
ianseer said:
um,,, yep u're right
I don't know, CMIIW, I already search the forum.... no one do that till now... so the oreo rom is unrootable then?
it feels like "they" dump us
Click to expand...
Click to collapse
I guess magisk works on Oreo and I'd don't then post bugs on magisk thread.
nevermind guys, already succeed installing twrp on global rom... I dunno what happened, already tried the fastboot devices command and it detected my device nicely, oem unlocking also works. but when to try installing recovery it says :
Code:
fastboot flash recovery recovery.img
Sending 'recovery' (25401 KB) FAILED (remote: 'Requested download size is more than max allowed
')
Finished. Total time: 0.018s
the solution for me was change the usb cable, and also restarting my windows 10. after that it still gave me same messages for 1 or 2 times, and then it works...
Code:
C:\android\platform-tools>fastboot flash recovery recovery.img
Sending 'recovery' (25401 KB) OKAY [ 0.607s]
Writing 'recovery' OKAY [ 0.018s]
Finished. Total time: 0.645s
Hope this will help anyone that needs it.
Thanks
ianseer said:
nevermind guys, already succeed installing twrp on global rom... I dunno what happened, already tried the fastboot devices command and it detected my device nicely, oem unlocking also works. but when to try installing recovery it says :
the solution for me was change the usb cable, and also restarting my windows 10. after that it still gave me same messages for 1 or 2 times, and then it works...
Hope this will help anyone that needs it.
Thanks
Click to expand...
Click to collapse
A question what will you achieve by rooting phone? When there is no custom ROMs
methuselah said:
A question what will you achieve by rooting phone? When there is no custom ROMs
Click to expand...
Click to collapse
Many apps i want to use, ask for root permission, for example : screen off camera, substratum, root explorer, and more
ianseer said:
Many apps i want to use, ask for root permission, for example : screen off camera, substratum, root explorer, and more
Click to expand...
Click to collapse
Omni rom.is there

Categories

Resources