Hi guys yesterday i tried flashing a img to my microSD wich i though was mmcblk0p8 but i think i was wrong and my device restarted and when it booted up it said "encryption unsucessfull" i tried to boot TWRP and it said "please enter password" i pressed cancel and went to wipe and i can say that i'm able to wipe system cache but if fails on DATA and Dalvik partitions
now I do have nvflash setup with all the blobs and a full backup but i don't know how to fix my DATA and dalvik partitions i tried to format my data partition using NVFLASH --format_partition 10 but it is stuck on Nvflash started!
please help me
noahvt said:
Hi guys yesterday i tried flashing a img to my microSD wich i though was mmcblk0p8 but i think i was wrong and my device restarted and when it booted up it said "encryption unsucessfull" i tried to boot TWRP and it said "please enter password" i pressed cancel and went to wipe and i can say that i'm able to wipe system cache but if fails on DATA and Dalvik partitions
now I do have nvflash setup with all the blobs and a full backup but i don't know how to fix my DATA and dalvik partitions i tried to format my data partition using NVFLASH --format_partition 10 but it is stuck on Nvflash started!
please help me
Click to expand...
Click to collapse
Dalvik stored on data partition. Try to format it with fastboot.
Code:
fastboot -i 0x0B05 -w -u
or
fastboot -i 0x0B05 erase userdata
Graiden05 said:
Dalvik stored on data partition. Try to format it with fastboot.
Code:
fastboot -i 0x0B05 -w -u
or
fastboot -i 0x0B05 erase userdata
Click to expand...
Click to collapse
Thanks man!!!!! I can't believe such a tiny command can do the job I tried a full nvflash restore and that didn't work
Sent from my C5303 using xda app-developers app
noahvt said:
Thanks man!!!!! I can't believe such a tiny command can do the job I tried a full nvflash restore and that didn't work
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
And just to let You know: internal user memory presented in file explorer as sdcard is a folder inside data partition(mmcblk0p8). And external microsd is mmcblk1p1.
i wanted to know if it is possible to format our system partition as f2fs and have it work our data partition on kitkat is already f2fs so are we able to do it to system? in twrp i attempted this by fro matting to f2fs but when restoring system it reformats system as ext 4 is there away around this? on twrps website there is a command to keep a the file system it is "tw_rm_rf – uses rm –rf instead of formatting system and data partitions, this option is used to prevent changes to the file system settings such as file system type, " i found it here http://www.teamw.in/twrp2-reference-guide would this help to do this? i don't know where to put this command in though
Edit: on a sidenote i formatted cache as f2fs and it booted
Edit 2: i looked at it again and cache was reformatted back to ext4
billycar11 said:
i wanted to know if it is possible to format our system partition as f2fs and have it work our data partition on kitkat is already f2fs so are we able to do it to system? in twrp i attempted this by fro matting to f2fs but when restoring system it reformats system as ext 4 is there away around this? on twrps website there is a command to keep a the file system it is "tw_rm_rf – uses rm –rf instead of formatting system and data partitions, this option is used to prevent changes to the file system settings such as file system type, " i found it here http://www.teamw.in/twrp2-reference-guide would this help to do this? i don't know where to put this command in though
Edit: on a sidenote i formatted cache as f2fs and it booted
Edit 2: i looked at it again and cache was reformatted back to ext4
Click to expand...
Click to collapse
Did you ever succeed in getting stock "DATA" partition to F2FS? I couldn't restore my backup and phone wouldn't boot anymore.. so went back to EXT4..
Maybe @djvita knows something, I think he has been experimenting a bit with F2FS..
StefanGA said:
Did you ever succeed in getting stock "DATA" partition to F2FS? I couldn't restore my backup and phone wouldn't boot anymore.. so went back to EXT4..
Maybe @djvita knows something, I think he has been experimenting a bit with F2FS..
Click to expand...
Click to collapse
yes i was able to get only the data partition to f2fs no other partition will stay another format once it boots it reformats or when restoring system in twrp it will restore the system partition as ext 4
billycar11 said:
yes i was able to get only the data partition to f2fs no other partition will stay another format once it boots it reformats or when restoring system in twrp it will restore the system partition as ext 4
Click to expand...
Click to collapse
interesting.. how did you do it? I did it in TWRP 2.8.1.0 via advanced wipe and after that got stuck on the motorola bootlogo..
That is the same thing I did but after whipeing I restored my data partition. I think the reason you got stuck in a bootloop is because you did not clear dalvic and cache or you do not have the kit Kat boot loader
billycar11 said:
That is the same thing I did but after whipeing I restored my data partition. I think the reason you got stuck in a bootloop is because you did not clear dalvic and cache or you do not have the kit Kat boot loader
Click to expand...
Click to collapse
I tried it again.. this time it worked.. I rebooted after format directly back into recovery and was then able to restore my data from ext4 to f2fs.. not sure, why it didn't work the first time around, but thanks for checking back!
Accidentally I deleted boot and boot1 partitions on my Mi4 while extending system partition. Could create system partitions as ext2 but I do not understand what type of filesystem boot and boot1 belong to. Could someone help in creating back the lost partitions? Thanks in advance
[update]
I think I messed up boot partition...so tried to flash rom via fastboot(since I created the system partition already). Now I can't flash recovery also. Can enter only fastboot mode.Is my mobile permanently bricked?
Hello, I would really appreciate your kind help solving a bit of a problem I have with my Moto G 4G
I had a problem with my google account where it wouldn't sync anymore and play store sopped working (says no connection even though is there).
Since I already encountered this problem before and solved it once by formatting cache, and data I tried to go into Recovery.
Here the oddities begin: TWRP doesn't load and gets stuck on splashscreen;
I searched for it and read that formatting cache and userdata would solve also this problem, so I guessed that formatting them from bootloader would have done the trick.
Unfortunately when I enter the command fastboot format cache or fastboot format userdata I get this:
formatting is not supported for filesystem with type 'raw'
Are some of my partitions corrupted?!
How can I solve this??
BTW I can boot into system and all is fine except the problem with the google account that led me to these findings.
albmanzi said:
Hello, I would really appreciate your kind help solving a bit of a problem I have with my Moto G 4G
I had a problem with my google account where it wouldn't sync anymore and play store sopped working (says no connection even though is there).
Since I already encountered this problem before and solved it once by formatting cache, and data I tried to go into Recovery.
Here the oddities begin: TWRP doesn't load and gets stuck on splashscreen;
I searched for it and read that formatting cache and userdata would solve also this problem, so I guessed that formatting them from bootloader would have done the trick.
Unfortunately when I enter the command fastboot format cache or fastboot format userdata I get this:
formatting is not supported for filesystem with type 'raw'
Are some of my partitions corrupted?!
How can I solve this??
BTW I can boot into system and all is fine except the problem with the google account that led me to these findings.
Click to expand...
Click to collapse
Have you tried reflashing TWRP through fastboot, like this
Code:
fastboot flash recovery recoveryimage.img
You could then wipe, or format these partitions in TWRP.
Professor Gibbins said:
Have you tried reflashing TWRP through fastboot, like this
Code:
fastboot flash recovery recoveryimage.img
You could then wipe, or format these partitions in TWRP.
Click to expand...
Click to collapse
I tried that already, albeit just reflashig TWRP 3.0 and not other recoveries... it didn't work, still keeps getting stuck at splash screen :crying:
Did you use
Code:
fastboot format cache
or
Code:
fastboot erase cache
Because the format seems to give that error and erase should not.
UPDATE: After reading your post it says you did indeed use format, not erase, so use
Code:
fastboot erase cache
fastboot erase userdata
Thanks, unfortunately it worked to solve just the recovery getting stuck, and I f*ed up other things in the process.
I still can't access to Google accounts, or create another, says connection error with google servers.
Since I had the SD card as internal storage before, erasing userdata caused the SD card to not be recognised anymore... I could format it to solve the problem, but I didn't have a recent backup so now I also need to try recovering that data. I know. I'm an idiot.
The strange thing is I even wiped Cache, Dalvik, Data and System and proceeded to flash a new ROM, and google account still doesn't work
There are so many variables that could be causing the Google account issue. Although, did you flash the stock rom or a custom rom?
I flashed 6.0.1 custom rom, Resurrection Remix
Google account issue got solved by simply doing another wipe and ROM flashing.
Now I have to deal with the corrupted microsd card issue I caused when i erased userdata...
I don't want to format the card before I can restore the data that was in there, there's still important stuff there, and last backup is too old.
When I'm in recovery with the phone connected to PC I can see the drive and windows says it has only 590MB of free space from a 7.42GB total; problem is when I open the drive it says it's empty.
When I put the microsd in a card reader instead, it does get a drive letter assigned but when I try to open it windows asks me to insert a disk.
Data is still there, it didn't got wiped with userdata... did it?!
I tried the method described in this guide http://forum.xda-developers.com/galaxy-s4/general/guide-internal-memory-data-recovery-t3093292 to recover mmcblk1p1 and mmcblk1p1p2 but the recuva scan I did to the generated virtual hard disk reported no deleted files and just the file indexervolumegrid in system volume information folder.
Now I'm going to try to use testdisk to see if i can repair the partition, but i'm no expert so I'm not sure how to do that.
albmanzi said:
Google account issue got solved by simply doing another wipe and ROM flashing.
Now I have to deal with the corrupted microsd card issue I caused when i erased userdata...
I don't want to format the card before I can restore the data that was in there, there's still important stuff there, and last backup is too old.
When I'm in recovery with the phone connected to PC I can see the drive and windows says it has only 590MB of free space from a 7.42GB total; problem is when I open the drive it says it's empty.
When I put the microsd in a card reader instead, it does get a drive letter assigned but when I try to open it windows asks me to insert a disk.
Data is still there, it didn't got wiped with userdata... did it?!
I tried the method described in this guide http://forum.xda-developers.com/galaxy-s4/general/guide-internal-memory-data-recovery-t3093292 to recover mmcblk1p1 and mmcblk1p1p2 but the recuva scan I did to the generated virtual hard disk reported no deleted files and just the file indexervolumegrid in system volume information folder.
Now I'm going to try to use testdisk to see if i can repair the partition, but i'm no expert so I'm not sure how to do that.
Click to expand...
Click to collapse
Unfortunaly the erase userdata command will also erase the internal SD card. This is because the shared internal 'SD card' is actually stored under the userdata partition, in /data/media.
Im not a data recovery expert, but i believe that recovering data deleted on solid state media is much more difficult than a magnetic disk. Also, that tutorial appears to be for a Samsung phone, so those are not the correct partitions.
As for repairing the partition, the userdata partition, and the /data/media directory inside it, is recreated when booting into a ROM.
Professor Gibbins said:
Unfortunaly the erase userdata command will also erase the internal SD card. This is because the shared internal 'SD card' is actually stored under the userdata partition, in /data/media.
Im not a data recovery expert, but i believe that recovering data deleted on solid state media is much more difficult than a magnetic disk. Also, that tutorial appears to be for a Samsung phone, so those are not the correct partitions.
As for repairing the partition, the userdata partition, and the /data/media directory inside it, is recreated when booting into a ROM.
Click to expand...
Click to collapse
Yeah, I can't find anything even with testdisk.... I am at a loss, fortunatyely the lost data isn't mission critical, nevertheless it forces me to repeat many hours of work.
Going to format the card.
Sorry to hear that. Although I suppose it's a good reminder of the importance of regular backups.
Hi!
My device was shutting down while I stay on recovery and the cache partition now is corrupted. (seems only read partition)
I try deleting cache on fastboot, reinstall rom, stock, an old twrp work but new twrp not, e2fsck on adb shell (only on loop boot),...
I can see the filesystem white loop boot, but e2fsck can't repair permisions or block (bigblock problem).
And I don't know why can't run on download mode.
Thanks
Did you do "fastboot erase cache" or "fastboot format cache"? If you did the former, try the latter instead.