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
Related
Just installed link2sd earlier (formatted partition as ext3). Wanted to flash a different rom. Trying to backup my phone, and clockworkmod tells me it can't mount sd-ext. Anyone know a reason and/or work around?
I think CWM works only with ext4 partition AFAIK. So, you can re-partition your sd card to a ext4 partition using CWM, or you can format the ext partition only to ext4 using a computer.
YouArePoop said:
Just installed link2sd earlier (formatted partition as ext3). Wanted to flash a different rom. Trying to backup my phone, and clockworkmod tells me it can't mount sd-ext. Anyone know a reason and/or work around?
Click to expand...
Click to collapse
which version of CWM have you got?
3.0.2.4, which I've used for a while now, always tries to back up my 6GB ext2 debian partition unless I remember to change cards first. no way I leave room in the vfat partition to back up that much data.
I'll put it up on 4shared if you want it.
mihir287 said:
I think CWM works only with ext4 partition AFAIK. So, you can re-partition your sd card to a ext4 partition using CWM, or you can format the ext partition only to ext4 using a computer.
Click to expand...
Click to collapse
Guess when I get home I'll copy the contents to computer, reformat, and copy back. Hopefully link2sd will notice the formatting has changed and reset itself
Sent from my LG-VM670 using XDA App
Doesn't work with extra either. Version 3.2.0.1 I believe it was.
Guess it doesn't really matter, can just use titanium since its all app stuff on there anyways...
Sent from my LG-VM670 using XDA App
i use CWM to back up my 512MB ext2 partition for my data2ext all the time (with the rest of the backup) and it seems to have no problem, and just to check i just mounted the partition in mounts and storage and it mounts fine. I know some recoveries ive used in the past on other phones would have problems with partitions that were not in 64-128-256-512-1024 MB, etc. format because of block size issue errors that i would get (when mounting or trying to set block size to 4096). I also found that when partitoning/formatting to ext2/3/4 some programs do not properly write the drive formatting and certain systems/recoveries/apps could not properly read them on the android. the best most consistent (android friendly) formats that i have gotten to date were in ubuntu (or any other) linux using "gparted". It seemed to always be the best and usually better than the format done by the phone recovery. Hope this helps. Sorry to drone on and on.
Partitioned originally with gparted. Have since resized to be 2048, and set its label to 'sd-ext'. Now instead of getting an error saying sd-ext might not be supported on my device, it just gives me a generic 'error mounting sd-ext'
I've had ext partition mounting problems before, I'm not sure if the cause is something to do with vold or what, but
after unmounting a sd card to exchange it with another one, it changes the device partitions in /dev/block like
/dev/block/mmcblk1p2
for the sd-ext partition instead of the normal
/dev/block/mmcblk0p2
you can see if this has happened by
Code:
ls /dev/block
in adb shell.
to mount it manually, if the numbering is off,
Code:
mount /dev/block/mmcblk1p2 /sd-ext
I've only had this happen with android running, but it might work in recovery too
Switched over to using data2ext. Mounts the 2nd partition as the /data partition instead of /sd-ext. Can manually mount 2nd as /sd-ext from within rom, but it doesn't carry over to recovery.
A possible solution... Create a symbolic link pointing /sd-ext to the 2nd partition? But then again, since /data now points to 2nd partition, is recovery picking up on that unknowingly and backing up the 2nd's contents when it thinks its backing up the normal /data?
I suppose I should investigate.
Edit: Yep it does backup the 2nd partition, thankfully. Just tried to install a theme made in UOT Kitchen, it borked some stuff, and the restore worked.
Sorry if i sound like a noob but can i take advantage of the ext3 partition on my SD using this version of CM?
I partitioned my SD using clockworkmod, which is why it's ext3.
only app i've tried is Link2SD but when i tell it there is an ext3 partition on the card it creates a script and asks me to reboot.
Once that's done and i access the app again it goes through the same motions and informs me that - "if im seeing this message then the partition is unable to be mounted during boot"
Appreciate any help
Here's a quick way to install Link2sd.
I preassume that your device is rooted and your sdcard data is backed up.I think,the mount script didn't work because of inappropriate attributes..Ok heres,how i installed Link2sd...
1.First of all download and install MiniTool Partition Wizard in your windows PC.
Connect your handset to the PC via USB.
2.Launch MiniTool Partition,you should see your SDcard mentioned in the list Under Disk 2 probably.
3.Right click your SDcard mentioned in the list, press "Move/Resize Partition"
4.In the Partition size,allocate bigger chunk of partition for primary partition.This is the partition your phone will access for general purpose.Say you allocate 7GB from your 8GB memory card.
Click OK.
5.Now Under disk 2. you will see and unpartitioned space of about 1GB.This partition will be used by link2sd.You may allocate your sdcard as you may wish.
6.Right click the upartitioned space to create a new partition under "Create As".If a warning popup asks for permission click YES.
7.Under New window Create As,choose "Primary".For File System type choose 'FAT32'.though you may choose among ext3 or ext4,either is supported by link2sd.NTFS is not supported by Link2sd or android OS.For partition size take whole unallocated space.Click on OK
8.Click Apply button<upper left corner in the screen>.
9.Restart your phone.
Again use your Link2sd app to create mount script.Now your app should work fine.
Don't forget to hit THANKS if i helped you.
I would not suggest you to create the Link2sd partition as a FAT32 one: this way when you will connect your phone to a PC through the USB cable Windows will mount all the 2 partitions automatically (with all negative consequences you can imagine); this issue will not happen on Linux, however; while with the Link2sd partition formatted as extX you will be able to use your linked apps while the phone is connected to your PC and the first partition is mounted, it doesn't matter if you are on Linux or Windows (tested )
Regarding your problem: try to tell the Link2sd script activator that your partition is an ext4 and see if it works.. I hope so, anyway let us know..
@brainvision
yeah thanks,extX would be better..bt i think windows doesn't mount two sdcard Fat32 partition at a time.i may be wrong in this term, bt sometime back,when i used to use rooted android 2.1,windows would mount only my 1st primary partition of sdcard..however under ubuntu..both partition would load bt without affecting the phone apps.
thinkfreedom said:
@brainvision
yeah thanks,extX would be better..bt i think windows doesn't mount two sdcard Fat32 partition at a time.i may be wrong in this term, bt sometime back,when i used to use rooted android 2.1,windows would mount only my 1st primary partition of sdcard..however under ubuntu..both partition would load bt without affecting the phone apps.
Click to expand...
Click to collapse
oh sorry I'm not a winZoZZ user since a lot of time!! I'm a slacker now!!
Regarding Linx OS: I set up my Slackware so that it doesn't auto mount external disk, so i can plug in the phone and activate the USB Mass storage without still mounting it: this way I can mount only the first partition; but in a auto-mount situation I fear that the the phone apps would be affected by USB Mass storage activation!
Hello!
I am running rooted stock Android 2.3 on LG E405 (no working 4.x ROMs exist for the device)
I have two questions:
1) What is the shell command to manually make android allow the PC to mount androids' (internal) partition as USB-drive? (I cannot think of right keywords to google this one up - please help!)
2) How does android determine which partition is which (i.e. which one to remount for the PC when connecting in "USB storage" mode), beside vold.fstab and init.rc? On android 2.3 that info is not in "framework-res.apk", so where is it? In the partition table itself?
Please help me search the forums for an answer. ANY advise is much appreciated!
This is why I ask:
I had switched data partition with internal sdcard partition.
Here's how:
Phone had a very small "/data" partition on /dev/block/mmcblk0p21 and large internal "/sdcard" partition on mmcblk0p20
So I reformatted mmcblk0p20 (ex-sdcard partition) into EXT4 and mmcblk0p21 (ex-data partition) into FAT32
Then I changed init.rc to mount mmcblk0p20 as /data type EXT4 and mmcblk0p21 as /sdcard type VFAT (mounting /sdcard was commented out in stock init.rc for some reason). This required modifying my boot image.
I have also set correct partition number in vold.fstab:
[#]dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host[/#]
So basicly I now have a large /data partition and small internal /sdcard.
I'm able install up to a gigabyte of APKs and it works fine.
However, when I connect to my PC via USB into "USB Storage" mode, the phone seems to still try to unmount what was previously sdcard partition (/dev/block/mmcblk0p20), instead of what is NOW an sdcard partition (/dev/block/mmcblk0p21)
I can still send files to the phone via wi-fi and ADB, but the ability to mount it directly would be nice.
If I accidentally select "erase internal sdcard" from storage menu, that will also most likely erase what is now my /data partition, softbricking the phone.
The "factory reset" option will probably only corrupt the sdcard.
There may be other problems with that.
I am also interested in mounting the data partition in this way. Does anyone know how to do it?
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.
When i was uploading new rom, partitions connect to one. Many roms have a problems with this. Second partition has a 0MB size. I try upload stock rom by flashtool and no results. I want to restore original size. How I can do this? My phone is sony xperia lt30p.
What ROM have you flashed? Have you done a clean install, means having wiped existing Android OS before?
What's the name of the mentioned 0MB partition?
BTW:
Android comes with standard partitons as
/boot
/system
/recovery
/data
/cache
/misc
and their sizes basically are hardcoded.
Never have noticed, heard or read that when a ROM gets flashed a partition with size of 0MB will be created.
Name se
jwoegerbauer said:
What ROM have you flashed? Have you done a clean install, means having wiped existing Android OS before?
What's the name of the mentioned 0MB partition?
BTW:
Android comes with standard partitons as
/boot
/system
/recovery
/data
/cache
/misc
and their sizes basically are hardcoded.
Never have noticed, heard or read that when a ROM gets flashed a partition with size of 0MB will be created.
Click to expand...
Click to collapse
The name second partition is ,,sdcard". Tt isn't sdcard it is internal memory for photos and the like things
jareczex said:
Name se
The name second partition is ,,sdcard". Tt isn't sdcard it is internal memory for photos and the like things
Click to expand...
Click to collapse
Don't confuse /sdard and sdcard.
With regards to /sdcard:
This is NOT a partition on the internal storage memory of the device but rather the ( external ) SD card.
With regards to sdcard:
This simply is a symbolic link to device's /data/media partition what is mounted as /storage/emulated/0
And How i Can restore default memory this partition? Partition with external sdcard has other name.
OK it's the partition named /data/media you're referring to.
If a partitition shows 0MB ( can't get mounted ) then this is because it probably is encrypted. Hence decrypt it. The common method is to perform a Factory Reset. If you've TWRP installed / at your fingertips then decrypting also can be done with TWRP.
This phone is other than many phones
For me, everything you post is crazy stuff: I can not understand what the problem really is.
Since Android is on the market, it has more or less the same partition layout as shown above. And I'm pretty sure your phone has this, too.
I mean about problem, when i am installing rom, show me comunicat ,,Error instaling zip file 'external_sd/android9 sony t/open_gapps-arm-9.0-pico-20201114.zip" and i wanna get rid of this problem, across restore this partition. Do you know, what i have a mean?
My last 2 cents here: Open Gapps isn't a ROM. It's merely a suite of re-compiled Google apps.
FYI: I no longer participate this thread. I hope for you others jump in.
ok, thank you for your help. Information for other people: I can't install apps on this roms, so i want to restore this partition