Database Info

[SOLVED] Plz help: my phone can't boot now

Dear all, I need your help ASAP.
My phone (rooted) doesn't boot now, adb does not recognizes, fastboot still ok. And I don't know what to do.
Recently I rooted my Desire S and succeeded with the stock ROM. After a coupe of days I dicided to flash Endymion, from here: http://forum.xda-developers.com/showthread.php?t=1310845
I downloaded Endymion 3.1 into SD, then used Rom Manager to flash it. But then it was not be able to reboot (stucked on splash screen).
After that I rebooted into recovery (4EXT) and formated system, data, cache, boot and retried to install Endymion 3.1.
But then it became worse, now I can't use adb (always says: device not found), normal boots always stucks at splash screen (with green "HTC"). No hard button can be used, I need to reboot by take off the battery, then put it back on.
fastboot still seems working fine if I reboot to fastboot mode, but when I try "fastboot erase ...", I get "remote: not allowed". But other commands (fastboot flash...) still ok.
4EXT recovery is also still working.
Please help me to install some ROM at least. A lot of thanks.

Not quite sure, but could it be a faulty eMMC chip? Since you did mention you pulled out the battery.
http://forum.xda-developers.com/showthread.php?t=1314629
I did have a similar problem before myself.

So can you get into the boot loader? I'm assuming so since u got into fast boot. I would try flashing an update.zip through there, such as a stock from containing recovery.img,system.img...etc.
Sent from my HTC Desire HD using xda premium

Thank you for replies.
@microlah: I think my problem is not eMMC because I did not get those errors.
@stumpyz9: Before trying to flash Endymion 3.1, I made a backup of the rooted Sense 3.0 through Rom Manager -> a collection of *.img files.
I have tried to boot into fastboot, and executed these commands:
fastboot erase boot -> Error: remote not allowed
fastboot erase recovery -> Error: remote not allowed
fastboot flash system system.img -> OK
fastboot flash boot boot.img -> OK
fastboot flash userdata data.img -> OK
fastboot flash recovery recovery.img -> OK
but after this, the phone still does not boot normally.
Please tell me if I did something wrong or not. I dont know how to make update.zip from *.img files, and dont know where to get and choose the right stock rom for my phone.

d_t_kien said:
Dear all, I need your help ASAP.
My phone (rooted) doesn't boot now, adb does not recognizes, fastboot still ok. And I don't know what to do.
Recently I rooted my Desire S and succeeded with the stock ROM. After a coupe of days I dicided to flash Endymion, from here: http://forum.xda-developers.com/showthread.php?t=1310845
I downloaded Endymion 3.1 into SD, then used Rom Manager to flash it. But then it was not be able to reboot (stucked on splash screen).
Click to expand...
Click to collapse
Are you S-OFF or htcdev unlocked ? If you're still S-on you have to manually flash boot.img with fastboot to get Endymion or others custom roms working.

d_t_kien said:
Thank you for replies.
@microlah: I think my problem is not eMMC because I did not get those errors.
@stumpyz9: Before trying to flash Endymion 3.1, I made a backup of the rooted Sense 3.0 through Rom Manager -> a collection of *.img files.
I have tried to boot into fastboot, and executed these commands:
fastboot erase boot -> Error: remote not allowed
fastboot erase recovery -> Error: remote not allowed
fastboot flash system system.img -> OK
fastboot flash boot boot.img -> OK
fastboot flash userdata data.img -> OK
fastboot flash recovery recovery.img -> OK
but after this, the phone still does not boot normally.
Please tell me if I did something wrong or not. I dont know how to make update.zip from *.img files, and dont know where to get and choose the right stock rom for my phone.
Click to expand...
Click to collapse
No font flash the backup .imgs flash a whole update zip through the boot loader. Use a stock rom that contains a bunch of .imgs. reflashing the ones u already have won't help
Sent from my HTC Desire HD using xda premium

Are you on hboot 2.00.002? If yes, did you flash the boot.img from Endymion via fastboot??
Sent from my iPod touch using Tapatalk

I used htcdev to unlock, it's still S-ON and HBOOT 2.00.002.
I did not flash boot.img of Endymion. Can I do that with "fastboot flash..." ?
Does it matter if "fastboot erase boot" makes error? (as I posted above)
Could you give me instructions step-by-step what I need to do, thank you.

hi all,
i have some problem like a d_t_kien (i have htcdev unlock dev. and HBOOT 2.00.002, 4EXT Recovery).... so after flash ROM (i try Reaper V2.0 - CM7mod) device has freeze on white HTC screen....
Please help us... how correctly flash Endymion ROM via fastboost..
Thanks

For both of you, here's the procedure. First, flash the ROM normally. Then, enter fastboot mode and flash the boot.img that came in the ZIP of your ROM.
Reference - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37

thx for your answer, its my bad, because i dont use search button... so i finf solution in this thread: http://forum.xda-developers.com/showthread.php?t=1314629
thx again .)

shrome99 said:
For both of you, here's the procedure. First, flash the ROM normally. Then, enter fastboot mode and flash the boot.img that came in the ZIP of your ROM.
Reference - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
Click to expand...
Click to collapse
Many thanks. That solved my problem.
Edmyrion works great now on my phone.

Glad i helped

Solved
Please marked this thread as solved. Thanks moderator.

d_t_kien said:
Please marked this thread as solved. Thanks moderator.
Click to expand...
Click to collapse
You'll have to do it yourself.... As OP, that's one of your privileges... Just go to the first post, select EDIT, then ADVANCED, and then you can edit the title of your thread and add "SOLVED" to the title.

[Q] AT&T HTC One X Bricked and need advice

Hi,
I have an AT&T HTC One X with no OS. I wiped it when I was trying to flash a custom ROM.
I only have access to bootloader and TWRP. Fastboot is working fine but TWRP is not. It does
mount properly, and adb sideload fails as well. I am using a Windows 7 PC and used a USB 2.0 port.
I installed some HTC Drivers from here:
http://forum.xda-developers.com/showthread.php?t=2217396
but it still says "device drivers failed to install" when I boot into recovery.
When I try to mount, it does not let me mount the sdcard. I see an E: drive on my
PC but it is inaccessible.
I have S-On, my bootloader is unlocked, and I have hboot version 2.14 if that info helps.
Does anybody have any suggestions as to what I can try next?

First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita

I helped him over teamviewer so I can clarify the situation. He can't mount in TWRP, it must of been a typo. It seems he cleared everything when he was trying to wipe to flash a rom. I believe it was ViperXL. He has no backup and sideload does not work as well. Hopefully that will clear things up a little bit more. I installed some newer HTC Drivers since the ones he had were old. The only thing that works seems to be fastboot at this point.
Sent from my HTC One X using Tapatalk

timmaaa said:
First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita
Click to expand...
Click to collapse
Sorry it was a Typo, I was not able to mount at all. The error said "unable to mount /sdcard"
Yes I have tried performing a factory reset from bootloader but the phone restarts and comes back to TWRP and then same thing.
I tried installing the ViperXL ROM but was not successful.
I was not able to flash the ROM and I tried to fix that but meanwhile looks like I wiped all what I had on my Phone, so no but I did try to flash a new boot.img after and it didnt work.
I dont think I have any TWRP backup on my phone, even though I tried flashing new TWRP but all failed.

Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita

timmaaa said:
Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita
Click to expand...
Click to collapse
So I followed all the above steps as noted; I had TWRP 2.6.3.0 earlier, I flashed the new TWRP 2.6.0.0 from the link you provided.All
successfully done.
-------------------------------------------------------------------------------------------------------
C:\Fastboot>fastboot devices
HT29WW300913 fastboot
C:\Fastboot>fastboot flash recovery "openrecovery-twrp-2.6
.0.0-evita.img"
sending 'recovery' (8000 KB)... OKAY [ 1.530s]
writing 'recovery'... OKAY [ 1.900s]
finished. total time: 3.430s
C:\Fastboot>fastboot erase cache
erasing 'cache'... OKAY [ 0.120s]
finished. total time: 0.120s
C:\Fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.070s]
finished. total time: 0.070s
---------------------------------------------------------------------------------------------------------
I rebooted into recovery, still came up as TWRP 2.6.3.0, then I went to TWRP reboot and chose Recovery, phone rebooted into TWRP 2.6.0.0
Tried mounting (could not select /sd card and /cache(expected as we erased it)) and ADB sideload, got the same errors as before. Unable to mount /sdcard.
Rebooted again and it displayed TWRP 2.6.3.0

Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita

timmaaa said:
Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did

And which recovery is currently installed?
Sent from my Evita

timmaaa said:
And which recovery is currently installed?
Sent from my Evita
Click to expand...
Click to collapse
Its 2.6.3.0, but in recovery when I go into option TWRP reboot and chose Recovery button, phone reboots into TWRP 2.6.0.0 and when I reboot it again, its 2.6.3.0

That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita

timmaaa said:
That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita
Click to expand...
Click to collapse
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?

tapukakababa said:
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?
Click to expand...
Click to collapse
Either one should be fine. If you have S-ON and the phone gets stuck on the HTC screen, you have to flash the boot.img. here's how to do it.
1. On your PC in the ViperXL.zip, take out the boot.img and put it in the directory where you have the adb and fastboot files.
2. Boot into fastboot.
3.Open cmd. Change the directory to the folder where you have those files.
4.type "fastboot flash boot boot.img"
5. Reboot the phone.
The phone should boot.
Sent from my One Xl using Tapatalk

Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita

timmaaa said:
Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita
Click to expand...
Click to collapse
So I flashed the boot image, then copied ViperXL and installed it through TWRP, it failed.

Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita

timmaaa said:
Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita
Click to expand...
Click to collapse
No I did not check the MD5, yes I'm on TWRP 2.6.0.0 and the errors it gives are as follows:
unable to mount '/cache'
unable to open zip
Error flashing zip

Always check the md5. It's possibly corrupt.
Sent from my Evita

timmaaa said:
Always check the md5. It's possibly corrupt.
Sent from my Evita
Click to expand...
Click to collapse
Yup redownloaded the file, checked/compared MD5, copied it back to the phone, removed the previous bad copy, flashed ROM successfully..., as per the message but system reboots to recovery.. is that expected?
And I still see both the TWRP's 2.6.3.0 and 2.6.0.0 the phone needs couple reboots in order to get to TWRP 2.6.0.0 but automatic reboot is in TWRP 2.6.3.0 whats the deal here?

I have no idea why your recovery is acting like that. Hopefully someone else can chime in on that.
Sent from my Evita

Recover a 4.4.4 downgrade brick! (Temporal solution)

So, i have noted a increased number of threads about people who have soft-bricked their phones downgrading from 4.4.4 GPE after recieving the OTA, since it includes a new partition table and there's no firmware image yet.
Worry not, i have found a solution for your problem. This method only let's you use custom ROMs (sadly), but it's meant to be a temporal solution while we wait for a 4.4.4 GPE image anyways.
So, without further ado, here's my fix:
You will need:
-The good ol' Android SDK
http://developer.android.com/sdk/index.html#download
-Motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
-A custom recovery. I recommend TWRP, since is the only one i have tested.
Official TWRP Images for Moto G: http://techerrata.com/file/twrp2/xt1032/openrecovery-twrp-2.7.1.1-xt1032.img
-The gpt.bin from 4.4.4 (this is the partition table)
I extracted it from the OTA file and uploaded to my Dropbox: https://dl.dropboxusercontent.com/u/82658555/gpt.bin
-A custom ROM of your choice (obligatory) + GApps (optional)
What to do:
Once you have the Android SDK, decompress the folder sdk/platform-tools in a place of your choice.
Inside this folder, put gpt.bin, the custom recovery image and the ROM and GApps zip's.
Start your phone on fastboot. Connect it.
Inside your decompressed platform-tools folder, hold shift and right click inside the folder. Select "Open command window here".
Make sure your phone is properly connected by typing "fastboot devices" (without the quotation marks). The command prompt should show your phone serial number.
Now we start the real deal. Fist of all, flash gpt.bin using this command:
fastboot flash partition gpt.bin
Make sure it ends on "OKAY"
Now, flash the recovery
fastboot flash recovery nameoftherecoveryfile.img
Once this is done, enter recovery using the fastboot menu on your phone (use Vol- to highlight "Recovery", and then press Vol+)
Now your phone should boot on recovery mode. If you recieve an error like "Can't mount /system/", don't worry, this is normal (there's no system partiton yet, after all). Now you can use ADB command with your PC. Once again, to be sure everything is connected properly,tyipe on the console:
adb devices
Once that is done, it's time to give your phone the custom ROM, so you can flash it. Type (or copy/paste)
adb push NameoftheROMfile.zip /sdcard/ NameoftheROMfile.zip
If you have GApps, do the same for those
adb push GApps.zip /sdcard/ GApps.zip
Now you can finally disconnect your phone from the PC! You are almost done, select "Install" in your recovery, and flash your ROM zip, then the GApps if you have them.
Once it's done, you can reboot to system.
And you will have a working Moto G again!!
Enjoy it, and don't brick it again

the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file

maurocds said:
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
Click to expand...
Click to collapse
From my experience, you don't have to enter sideload mode in recovery to push a file, sideload mode is for pushing OTAs. And remember, the ADB push command requires you to put the exact name of the file to transfer twice, that could have failed for you.
You can't use fastboot devices on recovery because you can only use ADB commands in recovery, you were supposed to use "adb devices".

Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.

masa86 said:
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
Click to expand...
Click to collapse
Not many people do NAND backups these days.
Sad, because they're really useful, and there wouldn't be as many "HALP BRICKED PHONE" threads.

It Doesn't work only say failed xD

Fresroqir said:
It Doesn't work only say failed xD
Click to expand...
Click to collapse
Care to explain what failed?

tatazeuz said:
Care to explain what failed?
Click to expand...
Click to collapse
The install for the custom rom and gapps

Fresroqir said:
The install for the custom rom and gapps
Click to expand...
Click to collapse
What error did you receive? Did you flashed gpt.bin correctly?

tatazeuz said:
What error did you receive? Did you flashed gpt.bin correctly?
Click to expand...
Click to collapse
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)

Fresroqir said:
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Click to expand...
Click to collapse
got.bin is the partition table of the Moto G. Its the file that indicates to the phone the size, name and number of partitions it should have.
So, I know TWRP said in red letters Failed, but I'm interested what is the specific error, what did it said on the command prompt of TWRP.

Error flashing zip sdcard pa falconzip
and then there comes this updating partitution details and do i need to put the rom twice in the cmd?

and do i need a cutom rom with 4.4.4????????

yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading

Fresroqir said:
and do i need a cutom rom with 4.4.4????????
Click to expand...
Click to collapse
maurocds said:
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Click to expand...
Click to collapse
I used the latest version of PA + Stock GApps

Thanks!
Edit: Nope... Still same problem. Looks like the gpt file flashed but everything else is the same.

It still doesn't work for me i got th whole time failed and i don't know what i need to do ;(
It says: Z:\New folder\Android>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.372s]
finished. total time: 0.399s
is that good?
EDIT:it looks that sideload works and not that push command
EDIT: nvm i am stuck at bootanimation
EDIT: this wont work it says failed all the time at twrp

I'm kind of confused. Why couldn't people downgrade and go back to stock by reflashing all of the files from an older stock image, including the motoboot and gpt? I would think this would work...although with people saying that they are unable to downgrade I'm not willing to try upgrading to 4.4.4 myself.
What errors are people seeing if they try to flash gpt and motoboot from, say, 4.4.2 stock or 4.4.2 GPE?
-- Nathan

not work for me..
every recovery stay on black screen and return vibration on touch screen
:/
help > http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228

i think this fix doesn't work because i can only sideload my roms and gapps xD

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..

Completely wiped phone

Well, I was messing around in TWRP without really knowing what I was doing, and selected all boxes in the Wipe section. Now, when I try to install the stock rom, I get an error telling me that gpt.bin can't be downgraded, and when I try to sideload a rom via TWRP, I get another error saying that the .zip file is invalid. Can't send pictures of anything on the phone since it is the only one I have. Sorry.

Are you using fastboot to flash stock ROM? Then simply leave the gpt.bin and bootloader.img and flash the rest. The phone should boot up fine.
For the Custom ROM, maybe the zip file is corrupted, have you compared SHA/MD5 hash sums if one is provided with the download? They are a good way to check that downloaded file is complete and not corrupted.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Are you using fastboot to flash stock ROM? Then simply leave the gpt.bin and bootloader.img and flash the rest. The phone should boot up fine.
For the Custom ROM, maybe the zip file is corrupted, have you compared SHA/MD5 hash sums if one is provided with the download? They are a good way to check that downloaded file is complete and not corrupted.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Already tried using fastboot and leaving the gpt out, but the phone keep getting stuck in a bootloop where it goes into recovery and tries to wipe something, and get an error(failed to mount /data). And the rom is not corrupted, since I tried a LOT of different sources, and nobody ever complained of it being corrupted or so.

ctcsilva said:
Already tried using fastboot and leaving the gpt out, but the phone keep getting stuck in a bootloop where it goes into recovery and tries to wipe something, and get an error(failed to mount /data). And the rom is not corrupted, since I tried a LOT of different sources, and nobody ever complained of it being corrupted or so.
Click to expand...
Click to collapse
i would suggest you to revert back to og firmware and then trying to flash twrp again then you can try to flash roms again
just go into fastboot and follow the instructions
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
i was too in this situation but in a different device hope this helps you

Amar 721 said:
i would suggest you to revert back to og firmware and then trying to flash twrp again then you can try to flash roms again
just go into fastboot and follow the instructions
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
i was too in this situation but in a different device hope this helps you
Click to expand...
Click to collapse
Can't actually install those firmwares too, since I keep getting the error followed by the bootloop.

ctcsilva said:
Can't actually install those firmwares too, since I keep getting the error followed by the bootloop.
Click to expand...
Click to collapse
you get errors on adb?
if no then just press the power and volume down button simultaneously then release the dont go into recovery wait there and follow the guide
let it be a side just after pressing the buttons dont go to recovery or anything just wait there and do relock the device bootloader using adb and fastboot you can get tutorials of it everywhere

Amar 721 said:
you get errors on adb?
if no then just press the power and volume down button simultaneously then release the dont go into recovery wait there and follow the guide
let it be a side just after pressing the buttons dont go to recovery or anything just wait there and do relock the device bootloader using adb and fastboot you can get tutorials of it everywhere
Click to expand...
Click to collapse
Yes, I do. Just tried right now.
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot oem lock begin
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.104s]
finished. total time: 0.105s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot flash partition zip/gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.168s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Along with version downgraded for primary_gpt on bootloader
The same thing with boot.img

@ctcsilva : Flash TWRP
Code:
fastboot flash recovery twrp.img
where twrp.img is the name of twrp file. Now boot into TWRP, go to Mount and check that /data is selected, if not, then mark it and select back.
Now go to Wipe>Advanced Wipe. Select data and tap Repair or Change File System. Now select Repair File system and swipe to confirm. Now go to Wipe> Factory Reset and swipe to confirm. Then Reboot>bootloader.
Connect the phone to pc and flash stock recovery
Code:
fastboot flash recovery recovery.img
, and boot into it. Press and hold power and press volume up key once, you should see the options now. Select factory reset and confirm. Now reflash the stock firmware from fastboot and see if it boots.
Edit :- Use this guide, do not attempt to relock bootloader, it won't lock unless every file is flashed, which is again impossible because the firmware is older than the one present in the phone.
Broadcasted from Zeta Reticuli

ctcsilva said:
Yes, I do. Just tried right now.
Along with version downgraded for primary_gpt on bootloader
The same thing with boot.img
Click to expand...
Click to collapse
oem is not unlocked : ( you should try asking help from a senior member like ishubhamsingh or other i guess they can definetly help you