Database Info

OnePlus one stuck at boot screen, please help!

FIxed with this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
My 64gb OnePlus One does not boot anymore.
I wiped system, data, cache, and dalvik and then flashed the 9/20 cm nightly, gapps, and supersu. The device rebooted and I saw the CM loading circle. However, next time I looked at the device, it was back at the Oneplus boot screen. After this, I have never been able to get it past this screen.
I have tried flashing the stock image using this guide (steps 1-3), as well as downloading the fastboot image from cnygn.com and flashing each img from fastboot using these commands:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Additionally I have tried flashing CM11 from TWRP, which still results in the same problem. I am able to access and use fastboot and twrp just fine.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
EDIT: I managed to install ColorOS with this guide, and it boots fine. However, I need CM with Google Play so after trying to get cm11s 33r with this guide, I'm back at square one with the phone not getting past the boot screen. Any ideas?

Hi so i guess you don't have a backup in the device,sometimes the easiest way to fix things is the right way just download this tool the one for your device 16/32gb the second version(v.2) put your phone in fastboot mode and hit cm update in the tool.
---------- Post added at 06:29 AM ---------- Previous post was at 06:26 AM ----------
http://www.youtube.com/watch?app=desktop&persist_app=1&v=5O2e_R_TbVg

android.345 said:
My 64gb OnePlus One does not boot anymore.
Click to expand...
Click to collapse
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
You should just need to do everything that's in the guide you linked, except the 4th step (you don't need to lock the bootloader). Flash the factory images and just reboot (don't flash/wipe/whatever anything else), it should be fine. Make sure you're flashing the right ones though, for example, since you have the 64GB version, you have to flash the userdata image for the 64GB OPO.
I don't think you should look for "1-click" toolkits, they can be more harmful than good since you don't know what you're actually doing.

bradipovsky said:
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
Click to expand...
Click to collapse
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'

android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...

bradipovsky said:
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
Click to expand...
Click to collapse
Do take a look at the update I have posted regarding ColorOS. Flashing a new rom from TWRP does not help. All fastboot commands work.
Also, I have been flashing userdata_64g.img

android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Same problem for me too. Device worked for a week with SOD-s that 2 days ago just rebooted and stay in the loop of logo 1+.. ??

Help unable to flash

I had cynogen mod installed and my phone rooted. Then all of a sudden i get a boot loop. I tried to flash but I receive an error FAILED <unable to flash write>. im able to go into recovery and boot loader. In my team win recovery in the terminal I get multiple errors saying "E:unable to mount '/data", "E:unable to mount /ata/media/TWRP/ .twrps when trying to read settings file" ,"E: No valid storage partitions found for MTP" (when i try to enable mtp), "E:unable to mount '/persist" and "E:unable to mount storage"
PLEASE HELP

I have same problem. Internal storage 0Mb. Can not mount /data /cache /sdcard. Using TWRP still see /system stucture but /sdcard /data are empty.
I was used NRT to flash other ROM or stock ROM, but 50% partition flashing is Failed (can not write flash...).
So sad! It seems my Nexus 5's flash chip is dead or device partition table is corrupt ?

ndminh82 said:
I have same problem. Internal storage 0Mb. Can not mount /data /cache /sdcard. Using TWRP still see /system stucture but /sdcard /data are empty.
I was used NRT to flash other ROM or stock ROM, but 50% partition flashing is Failed (can not write flash...).
So sad! It seems my Nexus 5's flash chip is dead or device partition table is corrupt ?
Click to expand...
Click to collapse
I looked into my partitions being corrupted but when i tried to repair them it said the file location didnt exist

Since you can boot into fastboot mode, did you try to flash the factory imgs? (except userdata.img to begin with).

Primokorn said:
Since you can boot into fastboot mode, did you try to flash the factory imgs? (except userdata.img to begin with).
Click to expand...
Click to collapse
yes im able to flash the system.img but not able to flash radio.img,bootloader.img,recovery.img,cache.img

dragonphx said:
yes im able to flash the system.img but not able to flash radio.img,bootloader.img,recovery.img,cache.img
Click to expand...
Click to collapse
With the flash-all script? Can you post the log?

Primokorn said:
With the flash-all script? Can you post the log?
Click to expand...
Click to collapse
Im using the nexus root toolkit, trying to do the flash stock and unroot for the boot loop. What flash.all script?

dragonphx said:
Im using the nexus root toolkit, trying to do the flash stock and unroot for the boot loop. What flash.all script?
Click to expand...
Click to collapse
A script in the official factory images to flash the partitions.

ive tried that before it still gives me the same errors FAILED <remote flash write fail>

please someone help me

My Nexus 5 was gone to repair center and they said its ROM Flash is corrupted. No replacement for it. I need to bring it to recycle bin!

I give up on life (I tried everything to fix the god forsaken phone and loosing hope)

This is a tangent to the issue I had Situated HERE. I am seriously giving up on hope and want help for the love of god. Semester is approaching and I need a functioning mobile
After "fixing" my isssue and being on Lolipop 5.0.2, I realised that my SU binary wasn't present, So I reboot into recovery to realise that CWM isn't present anymore.
Not a big issue, I plug it in and flash TWRP onto it using fasboot commands.
Now i go into recovery and Install Superuser.zip trough TWRP. Then I decide to make a backup of everything. Afterwards I rebooted
The boot logo (The logo in which it normally mentions that Bootloader is unlocked and blablabla) Apears. But then it closes. Apears again but then closes once more. It keep doing than until I boot it into bootloader and close it once arrived there.
If I try to get into TWRP again it closes and continue the cycle.
So I flashed in CWM recovery with the intention to Flash the Stock lolipop ZIP that I done before (which fixed it).
When I boot CWM however, I am presented with a bunch of command lines at the bottom saying
"E: can't mount cache/logs"
and other lines (If you want the exact command lines say so and I will go get them). I didn't flinched to it (sometimes weird **** happens like that and I got used to it) so I go into the install from sdcard. I get this amazing message:
E: cannot mount sdcard
And all gui is not even present. I close the phone and start panicking
################################################################
In other words I need help. I will be checking this thread all the time looking for any help. I am giving up. faced such a problem in my life. I am scared that I bricked the phone for good.
Here is all I know about said phone:
KITKAT MOTO G 4.4.4 from canada (obtained from WIND mobile) most likely XT1034 (Its a mono sim)
The bootloader is 41.18
I used TWRP 2.8.6.2 for xt1032 (This is probably why everything exploded. I didn't realised it was for xt1032)
And I used CWM touch 6.4.0.7 falcon
MORE INFO WILL BE COMING, But I am extremely stressed right now to the idea that I might killed it.
#######################################################################################
#######################################################################################
Here are the CWM error messages
ClockworkMod Recovery v6.0.4.7
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_Install
- Install ZIP
- Choose zip from /sdcard
E: can't mount /sdcard
-Choose zip from /sdcard
##CWM gui closes## only the command lines are showing.

################
Update 1. I calmed down. I searched the error message and found out that it could either be an issue with CWM being currupted. I will reflash it and bring details. If it doesn't work I will format cache (Wiping the cache seems to not work)
Formatting the cache seems to fix all the cache error messages. But the mounting of /sdcard still present an obstacle
################

Why not flash stock firmware?
motofirmware.center
Sent from my XT1031

#######################
Update 2
I did some research and found out that my sdcard might be on logical and not primary and a way to fix it is to use mini partition tool on it. I am hesitant to do this so I will search for other possible issues
############################################

ATTACK said:
Why not flash stock firmware?
motofirmware.center
Sent from my XT1031
Click to expand...
Click to collapse
Because I can't find it.
try to find a 4.4.4, xt1034 canada stock firmware, Not easy. I've look for around 3 hours without success.
I however found a flashable zip for it, so I need to make recovery work, Because to my knowledge you can't flash an entire zip from adb/fastboot
The site you provided doesn't contain the right firmware. I highly appreciate the help though.

####################################
update 3
I decided to try and sideload stock rom lolipop. Seems to be working. Will be updating the results.
Here are the result:
ON MOTO G
-Install zip from sideload
nothing unusual happens
ON ADB
- adb sideload "lolipop stock rom".zip
Loads.....
Sends.....
"*failed to write data 'protocolt fault <Coudn't read status: invalid argument'* "
BACK TO MOTO G
- cancel sideload
Restarting adbd....
status 0
finding update package.....
opening update package.....
E: Can't open /tmp/update.zip
(bad)
installation aborted.
Click to expand...
Click to collapse
So it doesn't work but I found that last bit interesting. I feel like things are clearing up even though no ones is helping me (except for ATTACK, thanks but I will need a lot more help than that ) So help is apreciated
######################################

What about this file? -> XT1034_FALCON-RETAIL-CA_5.0.2_LXB22.46-32_31_cid14_CFC_1FF.xml.zip
Taken from the factory image index thread. It's the full Retail Canadian 5.0.2 firmware for XT1034

Here are some links to the 4.4.4 firmware.
http://forum.xda-developers.com/showpost.php?p=54855457&postcount=354
EDIT: Here's another link that's probably faster then FileFactory.
http://yun.baidu.com/s/1eQ6iXR8
Sent from my XT1031

k-kuchen said:
What about this file? -> XT1034_FALCON-RETAIL-CA_5.0.2_LXB22.46-32_31_cid14_CFC_1FF.xml.zip
Taken from the factory image index thread. It's the full Retail Canadian 5.0.2 firmware for XT1034
Click to expand...
Click to collapse
If you look at the top of the thread you'll see a link pointing to the beggining of the file, The one who helped me told me to flash this exact file and made my moto to boot loop. Trust me, it's not the right one.
ATTACK said:
Here are some links to the 4.4.4 firmware.
http://forum.xda-developers.com/showpost.php?p=54855457&postcount=354
EDIT: Here's another link that's probably faster then FileFactory.
http://yun.baidu.com/s/1eQ6iXR8
Sent from my XT1031
Click to expand...
Click to collapse
YES, Omg I didn't knew lost posted Firmwares. Prase the mighty lost god. The first one is exactly it.
I don't mind waiting 1 or 2 hours. as long as I got it nicely set up for september 1 I'm a-ok
If it boots properly I owe you sir.

thegamerchunk1 said:
If you look at the top of the thread you'll see a link pointing to the beggining of the file, The one who helped me told me to flash this exact file and made my moto to boot loop. Trust me, it's not the right one.
Click to expand...
Click to collapse
The 4.4.4 is also in this thread
Edit: Hosted on AFH -> https://www.androidfilehost.com/?fid=24052804347795180

##############################
Update 4
I tried to restore stock firmware. Back to square 1.
Cache issues.... I fixed it
Can't mount /sdcard.... Can't fix it.
The logo is the only thing I see and whenever I try to close it by pressing the power button, it reboots into the logo screen.
The only way I can truly close it is by opening fastboot menu and closing it there.
WHY IS THIS HAPPENING IM LOOSING MY MIND
I beg someone, anyone, Help me...
######################################################################

##################################
Update 5 Final ****ing update ****
I wiped and formatted /sdcard with philz touch recovery.
It seems that I can mount the sdcard now but I can't flash any roms because it
"Failed to set up expected mounts for install"
I am seriously in the most depressed mood ever. I worked for 4 years in computer development and I never had this much trouble ever. I ****ing give up everything. If someone ever encounter this issue:
you are ****ed throw the moto g in the garbage its dead nada done.
If someone thinks the contrary tell me how I am supposed to fix this. I will check it in about 12 hours.

I will do anything that someone thinks is going to fix it.

So - after flashing stock firmware your device still won't boot?
How did you flash stock firmware?
Did you receive any errors while flashing stock firmware?
And you are able to flash a custom recovery (TWRP or similar)?
Sent from my XT1031

kinda urgent
@lost101 can you help him brother. He is in dire need.....

@thegamerchunk1 - You need to try to relax - you are making things more complicated than necessary.
It's an known issue that making a nandroid backup in certain versions of TWRP will cause all this. You need to start again.
Stop trying random fixes and fastboot flash the firmware image for your phone.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Provide a log of what happens when doing the fastboot commands.

ATTACK said:
So - after flashing stock firmware your device still won't boot?
How did you flash stock firmware?
Did you receive any errors while flashing stock firmware?
And you are able to flash a custom recovery (TWRP or similar)?
Sent from my XT1031
Click to expand...
Click to collapse
I flashed it using fastboot. here are the commands I used
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I recall seeing 3 errors. It was hours ago so I don't remember exactly where but it was before the system flashes. They were all similar error except for the end. Im gonna flash it again and see.
Yes I can flash custom recovery.
However I can't a right TWRP version for the phone. whenever I do flash it (TRWP 2.8.6.0 xt1032) and enter into recovery, the logo boots but closes right after
The only ones I could install were CWM and PHilz touch. But I can't install anything from sdcard because I either miss expected mounts (From formatting /sdcard/) or I can't mount /sdcard/.

lost101 said:
@thegamerchunk1 - You need to try to relax - you are making things more complicated than necessary.
It's an known issue that making a nandroid backup in certain versions of TWRP will cause all this. You need to start again.
Stop trying random fixes and fastboot flash the firmware image for your phone.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Provide a log of what happens when doing the fastboot commands.
Click to expand...
Click to collapse
Sorry. It was 2 am where I was.
I know how to fastboot flash. I'll try myself again and report myself again.
Also I wasn't expecting to see lost here.

thegamerchunk1 said:
Sorry. It was 2 am where I was.
I know how to fastboot flash. I'll try myself again and report myself again.
Also I wasn't expecting to see lost here.
Click to expand...
Click to collapse
Make sure to include the command: fastboot erase userdata

thegamerchunk1 said:
I flashed it using fastboot. here are the commands I used
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I recall seeing 3 errors. It was hours ago so I don't remember exactly where but it was before the system flashes. They were all similar error except for the end. Im gonna flash it again and see.
Yes I can flash custom recovery.
However I can't a right TWRP version for the phone. whenever I do flash it (TRWP 2.8.6.0 xt1032) and enter into recovery, the logo boots but closes right after
The only ones I could install were CWM and PHilz touch. But I can't install anything from sdcard because I either miss expected mounts (From formatting /sdcard/) or I can't mount /sdcard/.
Click to expand...
Click to collapse
Ok - after you retry flashing, please post those errors. May want to try using mfastboot instead of fastboot as well.
Also you could 'adb push ROM.zip' with a custom recovery, bypassing the sd card altogether, but I think you should get your device to boot first.
Sent from my XT1031

Hard bricked? Can't get into recovery, can't unlock bootloader

Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!

How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.

sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,

rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,

man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there

therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...

rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?

therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!

DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..

therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.

rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?

heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,

Bump!
Does anyone have any other suggestion please?
Thanks,

Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!

Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.

I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?

I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..

Please help me guys!!!!

Hey
I have a moto g(retasia version,xt1033).I accidentally ran the horrid command 'fastboot erase all'.This command erased the following partitions from my mobile->
Hob
Dhob
Fsc
Fsg
Cache
Clogo
User data
Modemst1
Modemst1
Carrier
Keystore.
After running this command my imei became zero and my device was not detecting any sim cards.So to restore the radio functionality of my phone,I obtained these partitions from a friend of mine who is having the same device and tried to restore the partitions using the app partitions backup and restore as well as using dd commands via adb.All these methods proceed flawlessly but I am not getting the signals back.
So if there is anyone here who has faced the same problem and has solved it someway please help me
P.S:Since these partitions are device specific and obviously in a secure read only kind of location,is it possible that these partitions are not getting written while running the dd commands?If so,does anyone here know how to bypass the securities and write these partitions?
Please help me guys.
Regards,
Gautham C S

Try to install you stock motorola 5.1 ROM by fastboot.

BryanByteZ said:
Try to install you stock motorola 5.1 ROM by fastboot.
Click to expand...
Click to collapse
These partitions don't come with the stock ROM.

try this....
http://forum.xda-developers.com/showthread.php?p=52648789#post52648789

tutul2336 said:
try this....
http://forum.xda-developers.com/showthread.php?p=52648789#post52648789
Click to expand...
Click to collapse
Tried that already:crying: