Related
When I boot into CWM, it says that it "failed to find userdata partition to mount". I'm assuming that's why I have no internal memory when I go to storage. Is there a way to fix this?
I think u need to flash data using flashtool (excluding everything else) or fastboot (fastboot userdata userdata.sinğ.
After tgat go to recovery and format it
Sent using C6833 - Carbon KitKat
ch3mn3y said:
I think u need to flash data using flashtool (excluding everything else) or fastboot (fastboot userdata userdata.sinğ.
After tgat go to recovery and format it
Sent using C6833 - Carbon KitKat
Click to expand...
Click to collapse
It worked. Thanks
I have the same problem. I tried extract ftf firmware, and flashing it with fastboot with command "fastboot flash userdata userdata.sin". I just get information on non existing userdata partition.
I can't wipe dalvik or factory reset, because userdata don't exist. I can install rom in recovery, but it just loops on android logo.
What can i try? i already flashed 4 different stock firmwares.
[edit]
ok, just use older flashtool. Newest will just brick your phone. Use 0.9.18.4 or older.
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:
xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.
hardest soft-bricked ever seen!!!
anybody haven't idea?
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---
Hello there,
I own a N5X with 32 GB of storage. After some failed flashing I reflashed stock, which works fine except that only 10.55 GB of storage are being shown in the settings.
I do not have any modifications at the moment other than TWRP and an unlocked bootloader.
I did some research and found that erasing and reflashing all these Android compenents should fix it (this example is for the N5):
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
flash boot boot.img
...which it didn't.
Does anyone have a solution? Is there any way to extend the partitions, maybe without wiping everything?
Thank you in advance
Tuxcraft32 said:
Hello there,
I own a N5X with 32 GB of storage. After some failed flashing I reflashed stock, which works fine except that only 10.55 GB of storage are being shown in the settings.
I do not have any modifications at the moment other than TWRP and an unlocked bootloader.
I did some research and found that erasing and reflashing all these Android compenents should fix it (this example is for the N5):
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
flash boot boot.img
...which it didn't.
Does anyone have a solution? Is there any way to extend the partitions, maybe without wiping everything?
Thank you in advance
Click to expand...
Click to collapse
None of those would fix the GPT partition table.
Try flashing the beta Android N OTA. That has fixed the GPT table for people who use 32GB TOT file on 16GB so perhaps it'll do the same for your reverse situation.
try fastboot format userdata. This will wipe everything tho. That should get you back to 32gb
Im not sure if there is a way to do it without wiping. Maybe flash twrp recovery and use the advanced menu to extend partition.
This worked for me:
Boot into TWRP
Choose "Wipe" -> "Advanced Wipe"
Select your "data" partition and choose "Repair or Change File System"
Select "Resize File System" - it should automatically expand your storage to fill the empty space.
Tuxcraft32 said:
Code:
fastboot flash userdata userdata.img
...which it didn't.
Does anyone have a solution? Is there any way to extend the partitions, maybe without wiping everything?
Thank you in advance
Click to expand...
Click to collapse
Your internal storage was downsized to 16 GB because of this command. The userdata.img formats the userdata partition to the base 5X storage size of 16 GB. Do not flash the userdata partition since you have a 32 GB phone.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Your internal storage was downsized to 16 GB because of this command. The userdata.img formats the userdata partition to the base 5X storage size of 16 GB. Do not flash the userdata partition since you have a 32 GB phone.
Click to expand...
Click to collapse
If that is what caused it (and the partition table is still fine), then he can probably do
fastboot erase userdata
fastboot format userdata
and it should be back to normal.
just do dalvik and cache reset from recovery
First, thank you for all of your replies <3.
TheBurgh said:
This worked for me:
Boot into TWRP
Choose "Wipe" -> "Advanced Wipe"
Select your "data" partition and choose "Repair or Change File System"
Select "Resize File System" - it should automatically expand your storage to fill the empty space.
Click to expand...
Click to collapse
Worked for me as well! I now have 24.89GB free (which is normal, isn't it?). Thanks a lot.
To you:
SlimSnoopOS said:
Your internal storage was downsized to 16 GB because of this command. The userdata.img formats the userdata partition to the base 5X storage size of 16 GB. Do not flash the userdata partition since you have a 32 GB phone.
Click to expand...
Click to collapse
and you:
beady_uk said:
try fastboot format userdata. This will wipe everything tho. That should get you back to 32gb
Click to expand...
Click to collapse
as well as you:
sfhub said:
If that is what caused it (and the partition table is still fine), then he can probably do
fastboot erase userdata
fastboot format userdata
and it should be back to normal.
Click to expand...
Click to collapse
– I think this is what I got wrong. The flash-all.sh reported an error and stopped after flashing the first couple of components so I flashed all the components manually, including the userdata.img. I will stay away from that next time.
sfhub said:
None of those would fix the GPT partition table.
Try flashing the beta Android N OTA. That has fixed the GPT table for people who use 32GB TOT file on 16GB so perhaps it'll do the same for your reverse situation.
Click to expand...
Click to collapse
Thank you for the suggestion, luckily this was not necessary.
ikyeye said:
just do dalvik and cache reset from recovery
Click to expand...
Click to collapse
I did that, with no effect.
TheBurgh said:
This worked for me:
Boot into TWRP
Choose "Wipe" -> "Advanced Wipe"
Select your "data" partition and choose "Repair or Change File System"
Select "Resize File System" - it should automatically expand your storage to fill the empty space.
Click to expand...
Click to collapse
THANK YOU! I'm glad I didn't listen to the advice to factory reset, etc. This fixed the size without losing anything.
Hi People, I'm a Moto G5 (XT1676) user. After unlocking bootloader, rooting, flashing ROMs, etc. I "broke" my phone and now mi IMEIs are 0 and lost my phone signal.
I've been reading posts of older versions (Moto G1, G3) that people seem to fix this problem by flashing oher phone's back up of fsc, hob and dhob partitions. The problem is that in my Moto G5 only fsc partition appears.
I'm not expert and don't understand too much , I'm just asking for your help please, my phone turned into a tablet .
Do anyone of you guys know what partition do I have to fix in this phone?
Can you upload a back up of those partitions for me please?
Flashing those partitions on other versions of the phone seem to fix signal problem leaving IMEI = 0, I just need my signal back.
Something that I don't know if is relevant is that when I messed up flashing things, reading posts around internet I used some commands that I think modified "persist" and "misc" partitions.
Can anyone upload those just in case too?
Sorry if something is wrong, english is not my native language.
Please help me!
EDIT!!:
I've managed to revive my phone restoring someone's persist backup from twrp, "Backup & Restore partitions" doesn't work. The file I used to fix this problem is in this link: https://mega.nz/#!Yd82hSZZ!vdmbqAG0bQhNyR5g95KOrZjVvBw2QDrirpOwhD96gPc
The only file i needed was the persist backup in that .rar
It's no my partition, I've found it around internet, searching everywhere, but it worked.
Thanks for all the people that tried to help me!
IMEI stayed 0 but my mobile signal is back!!
How to restore that partition?:
1-Install TWRP.
2-Go into Backup and make a backup of any partition there. This will create a partition folder inside TWRP folder.
3-Copy the persist backup I've shared into that backup folder.
4-Boot into twrp, restore and select persist.
5-Restore.
6-Flash stock rom again for your device.
I hope that this help anyone in the same situation. This works for Moto G5 Plus too from what I've been reading.
It would be nice if people comment their results so we can help others.
Attention!: This doesn't fix IMEI, it stays 0 but mobile signal is back.
Good Luck and thanks!
flash stock rom via fastboot
never play around with partitions unless you know what you are doing - simply typing in commands without knowing their meaning will likely muck up your device
find your stock rom firmware via the power of google
Open a command/terminal prompt where you have fastboot (if you have added fastboot to the environmental settings you can run it from any location)
The commands you will likely need are
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
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 have included fastboot in the link below - You will also need to download and install the moto usb drivers if you have not already done so
Platform-tools Download
TheFixItMan said:
flash stock rom via fastboot
never play around with partitions unless you know what you are doing - simply typing in commands without knowing their meaning will likely muck up your device
find your stock rom firmware via the power of google
Open a command/terminal prompt where you have fastboot (if you have added fastboot to the environmental settings you can run it from any location)
The commands you will likely need are
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
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 have included fastboot in the link below - You will also need to download and install the moto usb drivers if you have not already done so
Platform-tools Download
Click to expand...
Click to collapse
I've already tried flashing stock rom but the problem is still there, I've also tried some custom roms too without success.
I know is my fault, I touched where I didn't have to.
I don't know what else to try, I think flashing other's back up partitions is my last shot.
I don't know if you are a Moto G5 user, but if you are, can you share those partitions to me?
Thanks for your reply.
Your gonna need an EFS / QCN backup. Do you know how to set the modem to diagnostic mode?
SvenRL said:
Your gonna need an EFS / QCN backup. Do you know how to set the modem to diagnostic mode?
Click to expand...
Click to collapse
From what I've been reading Moto G doesn't have a EFS partition, I've found in other forums that Moto G4 series have that data in "Persist" partition, and that partition is the one i've been touching..
That's why I'm asking if someone can backup that partition and share to me.
There is an app that does the job "Partitions Backup & Restore", I think you need root to use it.
I need that Persist backup just to try fix my phone, if you have Moto G5, can you help me with that?
Yes I know how to set it into diagnostic mode. (I've been trying apps and programs that in that mode fix qualcomm devices without success).
Thanks for your reply!
Can someone please help me with a "persist" partition backup please? I really need help.
Hi Jerito. Sorry to take a few days to reply to your PM. Been away.
Not sure i can help with this one as am not knowledgeable about copying particular partitions.
About the most comprehensive rebuild i have ever done was what i posted about doing it file by file and if i was in your situation, well, thats what i'd try.
Can you somehow extract the partition you are after out of a ROM??
I'll do you a qcn backup, wait till early hours of Monday morning. I'm curious cause i have the same issue with my lenovo P2, no persist partition, but I think the persist partition is created from the fsg partition
astmacca said:
Hi Jerito. Sorry to take a few days to reply to your PM. Been away.
Not sure i can help with this one as am not knowledgeable about copying particular partitions.
About the most comprehensive rebuild i have ever done was what i posted about doing it file by file and if i was in your situation, well, thats what i'd try.
Can you somehow extract the partition you are after out of a ROM??
Click to expand...
Click to collapse
No problem, the best way I've found of doing a back up of that partition is through the app I've mentioned "Partition Backup and Restore", I will watch your post!
SvenRL said:
I'll do you a qcn backup, wait till early hours of Monday morning. I'm curious cause i have the same issue with my lenovo P2, no persist partition, but I think the persist partition is created from the fsg partition
Click to expand...
Click to collapse
Ok, I'll be waiting, thanks both!
Having an issue with my XL. I've been on LOS 15.1 for a while and wanted to try out the new Pie image. I made a backup and fired up fastboot as usual. I left the -w tag on as I wanted a complete wipe. Fastboot failed while wiping userdata and now bootloops twice before dumping me in stock recovery. I am completely unable to format data while in stock recovery. Same when I boot TWRP through the PC. Stock recovery says it can't write a new EXT4 partition and TWRP says I have no internal storage, then throws a ton of errors. Flashing OEM images from Google (Oreo or Pie) results in the same thing.
Any ideas? For the first time in years I am stumped.
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
Is your platform tools updated to the newest one?.
Edit I thought I was on the pixel 2 forum.
Could try to repartition the storage using a method similar to this one for the nexus 7? https://forum.xda-developers.com/nexus-7-2013/general/guide-repartition-nexus72013-to-t3599907
You would need to figure out the proper partition table for the Pixel though.
If you're 100% sure your platform-tools are fresh, you've got me stumped as well. I ran into tons of errors and such due to out of date tools when flashing Pie - obviously updating the tools fixed the issue.
Well I'd try external Type-C USB drive it enables external storage even if internal isn't working and fastboot flash your backup.
caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
i got the same problem, i just downloaded the Platform-Tools and opened it in PowerShell and executed flash-all script and it worked
Flash all script is good but I'd rather use external storage .. it's nice to know that there's more than one way to fix the problem outside of platform tools
I had issues with Pixel before and the multi partition thing screwed me up, but the Unified_Android_ToolKit was able to fix it for me. Worth a try for sure. Download Google Factory Image and use the tool.
Thanks for all the help everyone. Lots of good ideas here that I'll save for next time. Ten years tinkering with phones and I've never gotten this stuck.
In the end I flashed back to the factory Pixel XL image (October 2016). Like the previous attempts, it failed on accessing userdata. I used fastboot to flash a userdata.img file again, which similarly failed but somehow the phone still booted after about 20 minutes.
I found similar threads for other phones where people were in the same situation, but nothing they tried did the trick.
Back up and running now.
Sent from my Pixel XL using Tapatalk
Very odd. Based off your last post I'm going to assume you are not sure what triggered the issue?