[Q] It is possible to create own userdata.img ? - Android Q&A, Help & Troubleshooting

Currently, my phone goes to "encryption unsuccessful" screen. It happen because the userdata partition was not formated, the problem is, my phone storage only have 4gb, while the firmware is about 8gb, is it the emmc broken ? but i still can flash the phone normally
Now my phone storage have free space about 450 MB, and i decide to make my own userdata partition to make my phone work again (maybe), it is possible ? Sorry before for my bad english

Related

[Q] SD-Card Problem

hmm i got a little problem with my sd card ... i had 2 partitions on it and my os was recognizing the wrong one ... so i had to format it ... i deleted the 2 partitions (so i had unallocated space) and now i cant create a new partition or format it or whatever ...
its just like i never had one
is there any way to get some clean partition on it again?
btw i did that all with mini tool partition wizard home
nvm - bought a cardreader for ny pc and now i was able to create a new partition in the unallocated space so its useable again...

Problem with user partition on Itouch 701 tablet

First of all, I wanna thank all who may contribute to solve this problem, or just by simple reading. Thank you so much. Now then, the problem.
I have an Itouch (brand) 701 (model) tablet running rockchip 312x, 8 gb of rom, 1 gb ram, @ 1.2 ghz, double usb (one is a micro-usb), mini hdmi device. Since I wanted to modify the partitions of the user and userdata (due to have 1 gb of internal storage and 5.6 aprox gb of external storage) I backuped all the partitions so now I have the parameter and partitions saved on my PC. After that I modified the parameter file so I can resize the userdata and user (internal and external) partitions and then install bigger apks and games and stuff. I made the maths and resized the partitions with the parameter file only, flashed all again with the new hex values, and made a data and cache format so the changes can take effect. The problem was that the external partition could not be mounted anymore, and everytime I tried to mount it from the android menu it appears "the nand storage can be safely removed". Thinking that the problem may be in the \dev\vold\31:8 I made the following via adb:
adb shell
su
cd .\dev\vold\31:8
mkdosfs -F 32 \dev\vold\31:8
That gave me as a result an encrypted partition: I rebooted the device and after it booted, it requested me a password to unlock the partition. Flashed all again, and removed that lock but the user partition (the external storage) still keeps unmounted.
Any help will be very thankful.

how to make partition in zenfone 5 2gb a500cg ?

after installing an apps for galaxy s2, after restart my zenfone 5 ram 2gb lost it's partitions (it's erase something in my system folder). so, flashing via adb, fastboot,erase,format,factory reset,wipe,restore nand back up ( from zenfone 5 1gb, cause i didn't have nand back up) and other didn't work because partition of /system, /data, /dev, etc didn't exist. anyone can help me? :crying::crying::crying::crying: i just can use my phone in recovery and fastboot mode. someone say i must replace the motherboard. :crying::crying:

Internal Memory probably dead

Hello,
I need help for recover a Xiaomi android phone.
Internal memory soldered on the mainboard who is almost not repairable without IRDA is really a great thing, thank you to almost all manufacturers for that. A rpi like with micro sdcard for internal memory should be really a great thing for the future.
My problems :
- Recovery can't wipe any data because partition not mount anymore
- TWRP can't mount any partition : cache system and data
- I can create a new filesystem with mkfs.ext4 on all partitions but can't e2fsck because can't found superblock
- I try e2fsck by specified any superblocks listed during mkfs.ext4 but no one can read the partition
Now, I have an android phone with recovery working but cache, system and data partition seem corrupt and can't found any solutions for repair that.
There is any way to check each block like "badblocks" in the whole internal memory ?
I not found any tool for check the volume and e2fsck can't read the partition and can't check bad blocks.
If no ways for repair internal memory and memory is really dead, there is a way for modify permanently the /etc/fstab for mount at each restart cache system and data partition on the external sdcard ? (I can't boot and can't install any apps like link2sd for do that.)
Or a way for link sdcard to "/dev/block/mmcblk0" instead of "/dev/block/mmcblk1".
I hope there is a way for use sdcard or repair internal memory for not trash this phone not so old.
Thank you for your time and your help

Storage issue

I have the 32GB varient,
the usable Internal storage it shows is 23GB,
remaining free space it shows is: 2.9GB,
It is rooted, and I selected all files and folders (hidden files included) on Internal storage to check there total size:
it shows 10.04GB (on both ES and X-plore)
So,
out of 32GB, I only get 23GB for myself (lets just give 9GB away for the system, no big deal)
out of 23GB, I used 10.04GB and the remaining free space is just 2.9GB
So, 10.04+2.9 = 12.94GB, is all I get to use ? out of freakin 23GB ?!
Why !? Where the hell did 23-12.94 = 10.06GB go ?!!!
now, please dont tell me that the OS needs 9GB+10.06 = 19.06GB for the device to work correctly !
That too out of freakin 32GB ! Why would anyone call this phone a 32GB varient now ?
PS: I suck at maths.
It is something wrong to your data partition. try to fix it by using command flash 'fastboot flash data.img' separately over fastboot mode
extract data.img from the ROM you using
coolpixs4 said:
It is something wrong to your data partition. try to fix it by using command flash 'fastboot flash data.img' separately over fastboot mode
extract data.img from the ROM you using
Click to expand...
Click to collapse
will it wipe my data ?
jime1 said:
will it wipe my data ?
Click to expand...
Click to collapse
Of course, without wipe & erase data partition you cannot fix the issue since it is the wrong info of data partition leading to the OS cannot recognize the full size of data partition.

Categories

Resources