Hi guys! Its my first time posting a problem, i usually manage to fix it by reading and looking for info, but this time im really stuck
My cousins phone turned off one day and it never booted right again, got stuck in Moto logo... He tried to fix it (Not sure what he did, but my guess is that he somehow deleted a partition or someting), and now, it wont flash anything, just keep getting this error in every line:
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
Click to expand...
Click to collapse
I was able to unlock the bootloader (Device is UNLOCKED. Status: 3) but still cant flash anything, i tried almost every single post i could find in the web but no luck at all...
It boot directly into fastboot mode and when i press the power up button the logo image was replaced by this http://imgur.com/JH4CAq1
Bootloader version is 48.86 and when connected to the PC it is recognized as "Fastboot Titan S"
If anyone can help me i'll be really greatful!
Thanks for reading and sorry for my pooooor englando :laugh:
Related
New to rooting and playing around with the flashboot.
I have a pure edition Moto X lollipop. I decided to unlock (successful) and root (unsuccessful). Also, not sure if I enabled USB debugging before I started messing with fastboot. Now that I'm in loop, I cannot enable it.
My phone is now in constant loop, more specifically stuck on the blue world screen. It will not go any further. Here are the different solutions I've tried that have come up short:
- Fastboot menu cannot access "Recovery mode" it simply says "boot up failed."
- Tried flashing "openrecovery-twrp-2.8.3.0-ghost.img" file but I believe something must be incompatible and have now screwed up my system.
I just simply want to put it back to stock. Any help would be greatly appreciated. Please tell me I didn't stupidly brick my phone.
I have fixed this issue. This thread can be deleted/closed. Thank you for the search button!
how you solved this problem???
DocDroid said:
I have fixed this issue. This thread can be deleted/closed. Thank you for the search button!
Click to expand...
Click to collapse
HOW YOU recovered from problem??? i am having same one..
Neelesh16 said:
HOW YOU recovered from problem??? i am having same one..
Click to expand...
Click to collapse
Im having the same issue, Havent found a soluttion yet. gotta keep looking
I rest my Moto X Pure to Stock via CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162
- I believe Im locked out my phone now
Device is LOCKED Status Code: 0
Software Status: Modified
Any Fastboot(or mfastboot) code I try does this:
(bootloader) Permission denied
FAILED (Remote Failure)
So far its not looking good. Anyone have any ideas?
Hi!
I was given a xt890 that frezzes, like every xt890, in the red M.
I tryed to flash it but it doesnt work.
This is the deal, I can enter bootloader but no option works, you cant even power it off. You can select, factory, Normal, Recovery, BP tools and will freeze on the red M. Even if it is powered off and you plug in the charger it will freeze at the M, it wont show the battery animation.
I tryed to unlock the bootloader, I sent the code to Motorola, motorola sent me de unlock code but when I try to unlock it it says:
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 8.655s
In my opinion there is something related to the phone filesystem that is broken and I think that if I can unlock the bootloader I can flash a new firm,
Does anyone got some idea on how can I fix this?
Thank you!
alehawk said:
Hi!
I was given a xt890 that frezzes, like every xt890, in the red M.
I tryed to flash it but it doesnt work.
This is the deal, I can enter bootloader but no option works, you cant even power it off. You can select, factory, Normal, Recovery, BP tools and will freeze on the red M. Even if it is powered off and you plug in the charger it will freeze at the M, it wont show the battery animation.
I tryed to unlock the bootloader, I sent the code to Motorola, motorola sent me de unlock code but when I try to unlock it it says:
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 8.655s
In my opinion there is something related to the phone filesystem that is broken and I think that if I can unlock the bootloader I can flash a new firm,
Does anyone got some idea on how can I fix this?
Thank you!
Click to expand...
Click to collapse
Try flashing the stock firmware, as long as you use the correct firmware it will let you even though it is locked. What firmware is your phone using? Usually fastboot getvar all can show you more info about the phone.
Sent from my XT1095 using Tapatalk
Hi, this is what I thought but the thing is that I tryed 15 diferent firmwares and no one was succesful, all has problems erasing system. Maybe non of them are the one that came with the device but here in my country we got 3 companies, non of they worked.
Also if I flash recovery it says succesful but I cant boot into recovery, if I select recovery it stays on logo. I also tryed the unbrick thing with the files of the carrier rom and nothing happened, look like the bootloader its the same :/
If this is covered somewhere, please let me know.
While I was texting this morning, the phone turned off, and then got stuck on the white google logo.
I was able to get into recovery and when I tried to do anything (like look for old backups) nothing was there. When I try and do factory reset, it says unable to mount xxx (everything)
Try to push via adb has been unsuccessful. I've been trying toolkits to see if they have any magic in them, and no dice so far.
Any ideas or help?
Looking like I might have to contact Motorolla.
FWIW I was running rooted stock vzw image.
if you were running stock rooted and your phone is stuck in a loop you probably need to wipe your data, but since you can't wipe anything I would suggest booting into bootloader and flashing a fresh image. Make sure you check you md5's before flashing as you may have gotten a bad download!
sevenpioverthree said:
if you were running stock rooted and your phone is stuck in a loop you probably need to wipe your data, but since you can't wipe anything I would suggest booting into bootloader and flashing a fresh image. Make sure you check you md5's before flashing as you may have gotten a bad download!
Click to expand...
Click to collapse
thanks for the quick reply. maybe i'm doing something wrong, but trying to flash a fresh image isn't working either.
dopepope said:
thanks for the quick reply. maybe i'm doing something wrong, but trying to flash a fresh image isn't working either.
Click to expand...
Click to collapse
Can you list your steps in trying to flash a new image?
sevenpioverthree said:
Can you list your steps in trying to flash a new image?
Click to expand...
Click to collapse
of course.
following this tutorial:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
i've tried to manually flash via fastboot each portion, and ive tried the flash-all method
get FAILED <remote failure> when its pushing out.
(phone is in bootloader)
dopepope said:
of course.
following this tutorial:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
i've tried to manually flash via fastboot each portion, and ive tried the flash-all method
get FAILED <remote failure> when its pushing out.
(phone is in bootloader)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2603245
Not sure if that thread applies to you exactly, I read the first couple pages and it seems that the OP's phone somehow got relocked in the process. You can try running the fastboot oem unlock command again, updating your adb SDK, or trying one of the commands they list there although it's not for our phone so I'm not really sure what those commands will do
sevenpioverthree said:
http://forum.xda-developers.com/showthread.php?t=2603245
Not sure if that thread applies to you exactly, I read the first couple pages and it seems that the OP's phone somehow got relocked in the process. You can try running the fastboot oem unlock command again, updating your adb SDK, or trying one of the commands they list there although it's not for our phone so I'm not really sure what those commands will do
Click to expand...
Click to collapse
At this point I'll give anything a shot. Phone is in the RMA process (they're sending out a new one), so if I can get it working today I guess I can cancel the RMA, but I don't have high hopes.
Can't even re-lock the device:
<bootloader>
failed to erase parition
general lock failure!
sst lock failure!
FAILED <remote failure>
dopepope said:
Can't even re-lock the device:
<bootloader>
failed to erase parition
general lock failure!
sst lock failure!
FAILED <remote failure>
Click to expand...
Click to collapse
reading through the thread, i doubt there is hope. my only thought would be trying to flash the partition table first.
After nothing working got a replacement phone from Motorolla. Looks like I'm not the only one that had this particular issue. Not sure what the common factors are between us on this forum that have had a seemingly random hardware failure, but it doesn't give me a ton of confidence in the hardware. Good reminder to backup the stuff you care about
Hi,
I was unlocked and rooted and I tried using the NRT to flash the M system image. It worked and I got the phone to boot once. It went through the Android is upgrading process and I used it for a few seconds and then it froze. I rebooted it by holding the power button. It now will not leave the bootloader. When I try to start it just flashes back into the bootloader. In the BL log it says "failed to validate boot image: ref=-1" So I tried re-flashing both manually and in the NRT. This is the error I get when flashing
(bootloader) failed to write primary GPT
(bootlaoder) failed to flash partition
FAILED (remote failure)
Any help would be appreciated.
Thanks
Try fastboot erase before fastboot flash
-----_--------_--------_----------_---_--------_------------
....read......read more........think.........think more.......read...........read more........
Stop using a toolkit and do it manually https://developers.google.com/android/nexus/images?hl=en
I said that I did it both manually and with the toolkit. Sorry you feel that since I didn't want to type all that in you are better than me. I figured it out though. I couldn't get into any recovery so I used the toolkit to boot into the temporary twrp. Formatted all the partitions and got it to flash successfully.
From what I can tell it tried encrypting and it ruined the partitions.
My nexus 6 received the update by ota and I have experienced the same thing.... Tech support was no help telling me to go to a sprint store. I'm not sure what caused the issues here... My phone did the normal Android is upgrading thing and and I left I to do its thing it booted up and I used to it. Make a phone call. After the call my phone froze when I tried to open all apps. I restarted the phone in the same way the first post did. How ever my phone booted up to the new Android boot screen , however the phone restarted again and this time into the bootloader. Can anyone help me with this?
So recently i unlocked my bootloader so i could root my XT1092. But without knowing, i booted a file for an older android version while i was on 6.0. So then i was stuck at the end of the boot. Somebody told me to flash original stock files from motorola site. Did that but now i'm stuck at the 'bootloader unlocked' warning, and when i trie to charge it stays at battery low and it doesn't charge. Also when i trie to lock the bootloader again it says:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
OKAY [ 0.057s]
finished. total time: 0.063s
What should i do? PLEASE SOMEBODY HELP!!!
Sorry can't help..... But will you pls tell me what wrong step did you go through so that I can avoid them ( I need to unlock my X2)... Thanks!
had no problems with unlocking the bootloader. I flashed a twrp on the device and when i tried to get into recovery it said: no command
So i used another method that said i needed to boot a file but i forgot to read the comments and it was only for the moto x 2014 that are running on KITKAT. I was running on 6.0 and i saw that right after i booted the file. So always read the comments! That's the advice i can give. If you find a proper method please tell me too pls so i know what to do if i find a solution.
Ok, i fixed it i had some problems flashing the system img. but its solved.
OK i got the phone back working but it doesn't recognize my sim-card anymore and my internet speed is slow af. I got 101 kb/s for downloading and 22kb/s uploading speed. Sometimes i see a toast that says that it was unable to download the appendix?! What do i have to do to fix it?
benjg_ said:
OK i got the phone back working but it doesn't recognize my sim-card anymore and my internet speed is slow af. I got 101 kb/s for downloading and 22kb/s uploading speed. Sometimes i see a toast that says that it was unable to download the appendix?! What do i have to do to fix it?
Click to expand...
Click to collapse
You might have flashed an image for other variant. Now, flash the modems for your variant, you can find them in the threads! :fingers-crossed:
Could be true. Maybe it would work again if i install cyanogenmod 13?