Moto G xt1032 - TWRP Internal storage 0mb - Moto G Q&A, Help & Troubleshooting

Hi,
I have Moto G (XT1032) with Optimized Stock Rom 5.1 from this topic. It was alright couple of months, but today I woke up with my softbricked phone
It's stuck on Warning Bootloader unlocked, TWRP can't access any folder (although he see folder structure, so i guess it's good sign? :crying: ), all Internal Storage is displayed as 0MB, if I try to do anything I always get
Code:
"Failed to unmount '/system' /* /data etc. */ (Invalid Argument)"
Adb recognize device, but as unauthorized, when I start ADB sideload feature in TWRP, phone is recognized as sideloaded, but when i try to push rom it's say error: closed.
Can I somehow fix this phone, or is it permanent eMMC damage?

You have to give to Wipe/Format Data and Reboot/Recovery. Later go to wipe/avanced wipe and select: Dalvik/ART, cache, data and system.

cristiansuarezg7 said:
You have to give to Wipe/Format Data and Reboot/Recovery
Click to expand...
Click to collapse
I already tried it. I got spam of error Failed to unmount... and mkfs.f2fs error: "E:Unknown MTP message type: 1"
And Reboot/Recovery just shutdown phone, I have to get to recovery thru Fastboot (Power and Vol down).

Fikoblin said:
Hi,
I have Moto G (XT1032) with Optimized Stock Rom 5.1 from this topic. It was alright couple of months, but today I woke up with my softbricked phone
It's stuck on Warning Bootloader unlocked, TWRP can't access any folder (although he see folder structure, so i guess it's good sign? :crying: ), all Internal Storage is displayed as 0MB, if I try to do anything I always get
Code:
"Failed to unmount '/system' /* /data etc. */ (Invalid Argument)"
Adb recognize device, but as unauthorized, when I start ADB sideload feature in TWRP, phone is recognized as sideloaded, but when i try to push rom it's say error: closed.
Can I somehow fix this phone, or is it permanent eMMC damage?
Click to expand...
Click to collapse
Have you tried flashing unoptimized factory fimware through fastboot? To do this, enter fastboot mode and then flash the factory firmware for your device from here.

Do you have TWRP or Stock recovery?

Professor Gibbins said:
Have you tried flashing unoptimized factory fimware through fastboot? To do this, enter fastboot mode and then flash the factory firmware for your device from here.
Click to expand...
Click to collapse
Yes, I got error, like on this video:
Code:
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.209s
cristiansuarezg7 said:
Do you have TWRP or Stock recovery?
Click to expand...
Click to collapse
TWRP

Hmm... Possibly an issue with drivers, or incorrect factory firmware. Also, have you tried skipping GPT and motoboot.img?

Related

[Q] Two major problems combined completely block my phone

Hi,
so yeah... I got two fatal problems that completely block me from doing anything on my phone.
It started when suddenly my phone's screen turned black, and after a restart it keeps taking me to a screen when it asks for a password to decrypt my data, blocking me from reaching my phone.
So I wanted to recover the phone to fix it, but when i enter fastboot and choose recovery, after a few seconds it shows a picture of the android logo with an exclamation mark on it, and I cannot get into the recovery screen.
Each problem prevents me from fixing the other one, any ideas of how can I save my phone?
Download a custom recovery for crespo. Get your phone into fastmode mode and flash the recovery image.
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Then select recovery in fastboot menu.
Encrypt problem is reported in this thread earlier. You may have to do a full wipe and flash a new ROM.
I downloaded the google factory image, but when i run fastboot -w update image-soju-jzo54k.zip (tried two different ones), it fails when trying to write to the system partition (FAILED remote: Write fail).
the other partitions work, but something prevents me from updating the system partition no matter what zip i use, tried many.
any ideas?
Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.
_android_ said:
Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.
Click to expand...
Click to collapse
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?
loliori said:
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?
Click to expand...
Click to collapse
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)
_android_ said:
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)
Click to expand...
Click to collapse
ok so soju is the right one for me.
I followed your instructions and now, and it fails writing the system image, the cmd window pretty much looks like that:
checking product...
OKAY
...
... (more ok checks)
sending 'boot'
OKAY
more OK sendings
sending 'system'
OKAY
writing 'system'
FAILED (remote: Write Fail)
I also tried using the batch file and although the window closes before i can see if any error happened, i get the same "FAILWrite Fail" error in my fastboot screen status, so I assume the same problem occurs.
What about formatting system partition via cwm? Failed too?
no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)
loliori said:
no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)
Click to expand...
Click to collapse
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?
_android_ said:
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?
Click to expand...
Click to collapse
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.
loliori said:
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.
Click to expand...
Click to collapse
You should Install CM then gapps.
_android_ said:
You should Install CM then gapps.
Click to expand...
Click to collapse
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing
loliori said:
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing
Click to expand...
Click to collapse
Google factory images are only flashable via fastboot. But there may be CWMed (cooked) versions available in XDA.
It seems like no matter what rom i flash, it either gets stuck while the phone is loading, or the phone loads and i get this "type password to decrypt" window.
Is there a way to like hard-format my phone, or a way to fix my fastboot flashing problems?

[Q] Possibly a corrupted internal memory chip?

My Nexus 5 is under 2 months old.
I have TWRP flashed.
I also have Cyanogenmod flashed. (11-20130103-SNAPSHOT-M2-hammerhead)
Here's what happened.
Dropped the phone a few weeks back. Ordered a new screen.
Opened up the phone and switched the screen myself without any trouble.
Turned the phone on and everything was great for 2 days.
Then out of the blue the phone turned itself off in my pocket.
Had a hard time getting it to turn back on. Managed to do this a few times when I plugged the charger in.
It booted up normally but after a few hours it would turn off again.
This happened 3 times.
On the 4th time it started turning on normally without any problem but each time it would run the CM setup again.
All this time I was also unable to access the phone's internal storage via the USB. (debugging was turned on).
When the phone finishes the setup it shows that the internal storage is only 128MB.
When I plug the phone in this is what I see.
(see attachment)
When I boot into recovery and try to wipe the phone. This is what it says.
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Formatting Cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Does anyone have ANY ideas on what to try?
If there is more info needed about the phone just let me know. I'll get right back to you. I'm here all day.
pahh said:
My Nexus 5 is under 2 months old.
I have TWRP flashed.
I also have Cyanogenmod flashed. (11-20130103-SNAPSHOT-M2-hammerhead)
Here's what happened.
Dropped the phone a few weeks back. Ordered a new screen.
Opened up the phone and switched the screen myself without any trouble.
Turned the phone on and everything was great for 2 days.
Then out of the blue the phone turned itself off in my pocket.
Had a hard time getting it to turn back on. Managed to do this a few times when I plugged the charger in.
It booted up normally but after a few hours it would turn off again.
This happened 3 times.
On the 4th time it started turning on normally without any problem but each time it would run the CM setup again.
All this time I was also unable to access the phone's internal storage via the USB. (debugging was turned on).
When the phone finishes the setup it shows that the internal storage is only 128MB.
When I plug the phone in this is what I see.
(see attachment)
When I boot into recovery and try to wipe the phone. This is what it says.
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Formatting Cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Does anyone have ANY ideas on what to try?
If there is more info needed about the phone just let me know. I'll get right back to you. I'm here all day.
Click to expand...
Click to collapse
You might try flashing CWM recovery in fastboot to see if this will solve your issue. Downloadlink http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-hammerhead.img.
gee2012 said:
You might try flashing CWM recovery in fastboot to see if this will solve your issue.
Click to expand...
Click to collapse
How do I go about doing this?
I am unable to download any apps. The Play Store* app crashes as soon as I open it.
And can't store the img file on the internal memory, since I can't access it.
I am able to use adb however.
EDIT: Play Store not AppStore.
What does the appstore have to do with his recommendation?
Sent from Omni Nexus 5
AndroidSlave said:
What does the appstore have to do with his recommendation?
Sent from Omni Nexus 5
Click to expand...
Click to collapse
Did a quick google search on how to flash CWM and one of the guides told me...
"Download and install ROM Manager FREE [Market Link] on your Android device."
The other option was to store it on the internal memory.
Sadly both of these options aren't working for me.
EDIT: Sorry! I meant the Play Store.
You would flash it just like twrp via fastboot
Sent from Omni Nexus 5
AndroidSlave said:
You would flash it just like twrp via fastboot
Sent from Omni Nexus 5
Click to expand...
Click to collapse
This ^^ !!!
I tried flashing the recovery-clockwork-touch-6.0.4.5-hammerhead.img
Here's what I did.
Ran these commands.
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-hammerhead.img
This happened.
sending 'recovery' 11312KB
OKAY
writing 'recovery'...
OKAY
finished.
But the recovery mode still opens up TWRP...
pahh said:
I tried flashing the recovery-clockwork-touch-6.0.4.5-hammerhead.img
Here's what I did.
Ran these commands.
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-hammerhead.img
This happened.
sending 'recovery' 11312KB
OKAY
writing 'recovery'...
OKAY
finished.
But the recovery mode still opens up TWRP...
Click to expand...
Click to collapse
Did you restart bootloader after flash? Just double check now? If still twrp, maybe consider taking it back to stock.
rootSU said:
Did you restart bootloader after flash? Just double check now? If still twrp, maybe consider taking it back to stock.
Click to expand...
Click to collapse
Yes I did. I tried it 3 times. Going to try going back to stock now.
This happened when trying to flash stock...
C:\StockNexus5>fastboot flash bootloader bootloader.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.477s
pahh said:
This happened when trying to flash stock...
C:\StockNexus5>fastboot flash bootloader bootloader.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.477s
Click to expand...
Click to collapse
Looks like it, look here http://www.google.nl/url?sa=t&rct=j...pQhJJwQEs5bFuyY6nYlSRTA&bvm=bv.60983673,d.bGQ and here https://www.google.nl/search?q=FAIL...channel=rcs&gws_rd=cr&ei=xdH4Ut7yHqP_ywO_loAI for more info. You`ll probably have to send it in for repair.
Same problem with my Nexus 5.. Help!!
hey.. i m facing the same problem and got reseted with recovery mode.. nothing happens.. still showing memory 128 MB.. not choosing any network in the cell...
try 'fastboot boot' rather than 'fastboot flash'
Flashboot boot recovery.img. If your phone cannot flash memory it can still boot another recovery image.

"(bootloader) Preflash validation failed FAILED (remote failure)

Hi everyone, I hope you guys can get me a hand with this issue.
My Moto G, is briked. Its with bootloader version 41.18 (Lollipop) and its imposible to downgrade it becouse I get this message
"(bootloader) Preflash validation failed
FAILED (remote failure)ยจ
But is only that command, all others commands to flash the phone work properly (but I dont have any clue why its imposible to make Lollipop works, and I cant make KitKat runs with an 41.18 bootloader)
At this time, I dont care any more upgrade to Lollipop, I just want my phone back :crying:
Please help.
Thanks for you time.
unlock phone
preflash validation fail happens due to the locked bootloader . Either unlock bootloader to skip boot flash validation checks or flash stock factory image without unlockingbootloader in recovery mode . Standard recovery and factory firmware image .
I had this problem, I eventually took it back to the point of purchase after trying EVERYTHING! Have you tried flashing stock ROM ignoring the preflash validation error?
Sent from my XT1039 using XDA Free mobile app
You would have executed the following command when trying to downgrade to KitKat:
fastboot flash motoboot motoboot.img
It should not be done. Nevertheless, try installing paranoid android via a custom recovery.
fastboot flash recovery cwm-*.img
Once you are on 41.18 bootloader, you cannot flash an older motoboot.img over the existing image.
Even with a Lollipop bootloader, you can flash all images and the phone should boot.
I have an xt1032 and flash stock 4.4.4 Retail US with no problem.
ankushv said:
preflash validation fail happens due to the locked bootloader . Either unlock bootloader to skip boot flash validation checks or flash stock factory image without unlockingbootloader in recovery mode . Standard recovery and factory firmware image .
Click to expand...
Click to collapse
My bootloader is unlocked ("Status Code: 3"), but I cant flash the 41.13 bootloader, neverthles, I can re-flash the 41.18 without problem.
jasond567 said:
I had this problem, I eventually took it back to the point of purchase after trying EVERYTHING! Have you tried flashing stock ROM ignoring the preflash validation error?
Click to expand...
Click to collapse
Yes, if I flash my Stock ROM (Retail LATAM) it's never pass the "Warning Bootloader", just keep there until I turn it off. If I flash an 5.0.2 Rom, when I start the phone, takes me back to the bootloader with "Boot up failed" message
layman806 said:
You would have executed the following command when trying to downgrade to KitKat:
fastboot flash motoboot motoboot.img
It should not be done. Nevertheless, try installing paranoid android via a custom recovery.
fastboot flash recovery cwm-*.img
Click to expand...
Click to collapse
The problem is that I cant flash any recovery, I try CWM and TWRP. Always gives me an errero when I try too boot in to Recovery Mode.
Are you flashing the correct recovery? Try the latest Philz for your model of phone. The xt1032 is also known as falcon.
What errors are you getting when trying to flash recovery in fastboot?
audit13 said:
Once you are on 41.18 bootloader, you cannot flash an older motoboot.img over the existing image.
Even with a Lollipop bootloader, you can flash all images and the phone should boot.
I have an xt1032 and flash stock 4.4.4 Retail US with no problem.
Click to expand...
Click to collapse
Yep, I try installing Lollipop firmwares with "fastboot flash ......" but no one work
I have an XT1040, and there isnt an official 5.0.2 for this version of Moto G, but it should works, no?
audit13 said:
Are you flashing the correct recovery? Try the latest Philz for your model of phone. The xt1032 is also known as falcon.
What errors are you getting when trying to flash recovery in fastboot?
Click to expand...
Click to collapse
You were right! I was flashing a wrong recovery, I have XT1040 and for this one the name is "Peregrine", I already installed CWM and TWRP (both works, but no one read the SD Card)
I found an NIGHTLESS CyanogenMOD 12 for XT1040 but when I try to install it. I get this message (installing de *.zip with TWRP and CWM):
Code:
E: Unable to mount "/data"
E: Unable to mount "/cache"
E: Unable to mount "/system"
E: Unable to mount internal storage
Any ideas? :crying:
iyurcic95 said:
Yep, I try installing Lollipop firmwares with "fastboot flash ......" but no one work
I have an XT1040, and there isnt an official 5.0.2 for this version of Moto G, but it should works, no?
You were right! I was flashing a wrong recovery, I have XT1040 and for this one the name is "Peregrine", I already installed CWM and TWRP (both works, but no one read the SD Card)
I found an NIGHTLESS CyanogenMOD 12 for XT1040 but when I try to install it. I get this message (installing de *.zip with TWRP and CWM):
Code:
E: Unable to mount "/data"
E: Unable to mount "/cache"
E: Unable to mount "/system"
E: Unable to mount internal storage
Any ideas? :crying:
Click to expand...
Click to collapse
First, format /data/media
Then, /system
Then, /cache
Then, try to install the ROM.
Are you running GPE version of Lollipop on your xt1040? If you are, you may need to re-install stock 4.4.4, including flashing gpt.bin because the partition sizes may be slightly different between stock Lollipop and GPE Lollipop.
layman806 said:
First, format /data/media
Then, /system
Then, /cache
Then, try to install the ROM.
Click to expand...
Click to collapse
I'll try, but, where I should do that? I'm kind of lost with all this.
audit13 said:
Are you running GPE version of Lollipop on your xt1040? If you are, you may need to re-install stock 4.4.4, including flashing gpt.bin because the partition sizes may be slightly different between stock Lollipop and GPE Lollipop.
Click to expand...
Click to collapse
No, I dont install the GPE in the XT1040. Maybe could be what are you saying. Yesterday, I cant remember what I was trying to install and in fastboot, while I was flashing, said "Image is too large", but in de DOS windows on PC, it says "OK"
The issue is that I cant do a downgrade of gpt and de motoboot.
So, I should install 4.4.4 KitKat, (without flashing those 2 files) and try with the recovery installing CyanogenMOD 12? Or CMod12 not uses 41.18 bootloader?
Edit: I think that I cant install KitKat, bootloader gives me "Image is too large", the DOS windows says "OK", but Im thinking that really its not OK.
I install """succesfully""" an 5.0.2 Retail of Brazil, but for the XT1033 version. Really, I dont know if is GPE, but I was able to install all the files and the fastboot dont showme the "Image is to large" message.
Edit2: Withi is command in Terminal of TWRP
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
When I try to install the CyanogenMOD's zip, says "Unable to mount /system". So I think I fix the problem with /data. But if I'm right, now what?
Since your bootloader is unlocked and you never flashed a GPE ROM, go back to the start.
If you want to install a custom ROM, flash the recovery for your phone. If you get an error message in fastboot, write it down and post it here.
If you want to flash back to a stock ROM, are you flashing every partition except motoboot.img? Are you erasing cache and userdata at the end?
audit13 said:
Since your bootloader is unlocked and you never flashed a GPE ROM, go back to the start.
If you want to install a custom ROM, flash the recovery for your phone. If you get an error message in fastboot, write it down and post it here.
If you want to flash back to a stock ROM, are you flashing every partition except motoboot.img? Are you erasing cache and userdata at the end?
Click to expand...
Click to collapse
I cant flash any stock ROM for my phone yet becouse, stocks ROMs are until 4.4.4 KitKat using bootloader 41.13. and y cant downgrade my 41.18 bootloader
I am trying to instal CyanogenMOD 12 from my recovery (CWM and TWRP works properly) but I get this message
Code:
"E: Unable tu mount /system"
Here is a photo of the error
http://imageshack.com/a/img661/1201/n9u9Jy.jpg
Edit: I try "fastboot erase system" and "fastboot format system"... Both are done succesfuly, but I stil geting the same error. (Also, I cant mount /storage/sdcard1)
Where did you get the Lollipop bootloader?
Did you try to use fastboot or mfastboot to flash a stock ROM. I have an xt1032 with 41.18 and I can flash stock 4.4.4 ROM.
audit13 said:
Where did you get the Lollipop bootloader?
Did you try to use fastboot or mfastboot to flash a stock ROM. I have an xt1032 with 41.18 and I can flash stock 4.4.4 ROM.
Click to expand...
Click to collapse
I get it when I flash with fastboot an firmware from Brasil wich have 5.0.2.
I will try installing the firmware you have, could you paste me a link please? Is with Recovery installation or with fastboot?
You need to download the stock 4.4.4 firmware for your phone and follow this guide: http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
Did you install the right recovery? Try using Philz for the peregrine to install custom ROM: http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-philz-touch-t2827332
audit13 said:
You need to download the stock 4.4.4 firmware for your phone and follow this guide: http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
Did you install the right recovery? Try using Philz for the peregrine to install custom ROM: http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-philz-touch-t2827332
Click to expand...
Click to collapse
I followed the first guide and in the DOS window where you put the commands "fastboot flash...." everything goes "OK", but in the phone, the fastboot says "Image is to large" when is going to flash the "system" so Im thinking that its not flashing really
After reboots, the phones dont go further than "Warning Bootloader Unlocked"
I installed Philz for Peregrine, I try to install 2 customs ROMs differetns for XT1040 and I get
Code:
Opening update package...
Installing update...
detected filesystem ext4 for /dev/block/plataform/msm_sdcc.1/by-name/system at /system: invalid argument
unmount of /system failed; no such volume
detected filesystem f2fs for /dev/block/plataform
E: Error in /tmp/update.zip
(Status 1)
Installation aborted.
I 'm about to give up
After flashing the gpt.bin file, type fastboot reboot-bootloader and continue flashing. Maybe this will help.
did you find a way to fix it yet?
im having the same issue. and not able to do anything, i tried flashing cm12 didnt work.

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!

Please help me about hardbrick

My phone:
Huawei Mate 8 NXT-L29C636 (Last update was b193)
Output of DC-Unlocker (now):
Found Phone : HUAWEI NXT-L29
Model : Huawei phone in fastboot mode
IMEI : ***************
Serial NR. : QHC0216313******
Firmware : NXT-C900B192
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Click to expand...
Click to collapse
My story:
I couldn't get any update from Settings>Update. My phone was EMUI4 (Android 6). I wanted to EMUI5 (Android 7). So I used firmware finder in phone(I mean, it's not windows app, it was android app). I thought me to need to install it version by version. So first, I selected b202 (there was it after b198) and I used to proxy to install. The phone downloaded the firmware and rebooted itself. When installing (It was %2), rebooted again. And now my phone is boot-looping.
Detail:
I can install TWRP or stock recovery via Multi-Tool 8. Also fastboot is working.
Note:
-Stock recovery dosen't install update.app from sd-card. Because (vol-)+(vol+)+power dosen't run the installer. The recovery is opening when I click those keys.
-Stock recovery dosen't have "download&install" option. Ability options: "Reboot system now", "Wipe Data/factory reset", "Wipe cache partitions". ("Wipe Data/factory reset" dosen't work.)
-Also I tried this guide. But I have error thats:
"Failed to mount '/3rdmodem' (Invalid argument)"
"Failed to mount '/cust' (Invalid argument)"
"Failed to mount '/data' (Invalid argument)"
"Unable to mount storage"
-TWRP says that "No OS Installed!"
Multi-Tool 8 Unbrick Outputs:
20:30:53: All images are found, everything is ready for the unbricking process.
20:30:55: Unbricking started. Your computer may freezes during the process.
20:30:55: flash boot "C:\Users\samed\Desktop\huawei\bicak\Unbrick\boot.img"
20:30:56: The Boot image is flashing successfully
20:30:56: flash system "C:\Users\samed\Desktop\huawei\bicak\Unbrick\system.img"
20:32:15: The System image is flashing successfully
20:32:15: flash cust "C:\Users\samed\Desktop\huawei\bicak\Unbrick\cust.img"
20:32:22: The Cust image is flashing successfully
20:32:22: flash recovery "C:\Users\samed\Desktop\huawei\bicak\Unbrick\recovery.img"
20:32:24: The Recovery image is flashing successfully
20:32:24: flash userdata "C:\Users\samed\Desktop\huawei\bicak\Unbrick\userdata.img"
20:32:29: target reported max download size of 471859200 bytes
sending 'userdata' (155193 KB)...
OKAY [ 3.425s]
writing 'userdata'...
OKAY [ 1.219s]
finished. total time: 4.644s
20:32:29: Error#1
20:32:29: Completed
20:32:29: Something went wrong (((
Click to expand...
Click to collapse
So, I don't know what I will do. DC-Phoenix is not free. But if it will be fix, I can buy.
Just give me any idea. I need to help.
- UPDATE -
I haven't access TWRP or stock recovery anymore. Because I tried to restore old backup (from another Mate8 L29 user) and now I getting this errors:
After logo I'm getting this error:
RESCUE MODE
Attention!
Please update system again.
Error!
Func NO : 8 (hifi image)
Error NO : 1 (security verify failed!)
Click to expand...
Click to collapse
I'm still start fastboot.
bro if you able to access fastboot mode so its easy you can do anything whatever you want,
see my case,...
https://forum.xda-developers.com/mate-8/help/flash-wrong-file-device-unknown-t3746905
Mr Hassan said:
bro if you able to access fastboot mode so its easy you can do anything whatever you want,
see my case,...
https://forum.xda-developers.com/mate-8/help/flash-wrong-file-device-unknown-t3746905
Click to expand...
Click to collapse
No you are wrong, I can access fastboot but the phone dosen't let me do anything. For example, now I getting hifi error. I'm trying this: "fastboot hifi FW_HIFI.img" or "fastboot erase hifi" and the phone is responding: "FAILED (remote: Command not allowed)".
My phone is unlocked! But I can't do anything whatever I want.
download the uni android tool crack and flash the update.app via fastboot,
Mr Hassan said:
download the uni android tool crack and flash the update.app via fastboot,
Click to expand...
Click to collapse
Alot tools (aka, Uni-Android Tools) need to access phone via ADB. In fact, if I can connect the phone via adb or COMport, I can do everything.
So if you know how to do "flash the update.app via fastboot", tell me please. But I don't think do it with basic tools.
bro, i,m also talk about fastboot mode flash, yes its possible, you can download UAT crack , goto huwei section, select huawei flasher, select update.app file, hold VOL _ connect power cable its must be in fastboot mode, now Press start flash, thats it

Categories

Resources