Hello,
since updating my ROM to crDroid 6.9, I try in vain to set up my 64GB sd-card on my Redmi Note 7 as internal memory. The error message from the log file is:
[08-30 15:09:33.190 2059:2059 E/StorageSettings]
Failed to partition
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.os.storage.VolumeInfo.getId()' on a null object reference
at com.android.settings.deviceinfo.StorageWizardFormatProgress$PartitionTask.doInBackground(StorageWizardFormatProgress.java:98)
at com.android.settings.deviceinfo.StorageWizardFormatProgress$PartitionTask.doInBackground(StorageWizardFormatProgress.java:80)
at android.os.AsyncTask$3.call(AsyncTask.java:378)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:289)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)
Click to expand...
Click to collapse
In "Settings - Memory", after two more attempts, it was displayed that the memory was damaged. However, it could then easily be set up as an external memory.
Is this a ROM problem or is it the smartphone hardware?
Related
Hey guys
This is my 3rd time rooting my phone and I keep getting the error
unable to mount to /dev/block/mmcblk1p1 when trying to run the update.
I can not even see my SD card inside android.
I have already reformatted my card to see if that would fix the problem.
Is there some mount command I can run from root to fix this issue?
Thanks!
fikal1 said:
Hey guys
This is my 3rd time rooting my phone and I keep getting the error
unable to mount to /dev/block/mmcblk1p1 when trying to run the update.
I can not even see my SD card inside android.
I have already reformatted my card to see if that would fix the problem.
Is there some mount command I can run from root to fix this issue?
Thanks!
Click to expand...
Click to collapse
This should go in Q&A, really, but here goes.
There are four possible causes:
1. SDcard failure (try another to eliminate this prob)
2. SDcard corruption (try another OS to format it, like an old smartphone or linux)
3. DI Software corruption (least likely, but can be eliminated by a bootloader PB31IMG.zip flash -- know that this fix would blank all your userdata, apps, settings, not stored outside of the 1gb nand&RAM).
4 DI Hardware failure (this possiblity is why I hated the rapid sdcard eject/insert method--that sdcard lock mechanism is just a itty bit of spring steel and an itty bitty little latch) -- how to eliminate? try the card in a card reader or device.
Good luck!
what was the file system type that you partition the card to?
Its fat32, and thats what I reformatted it to also.
Hi,
I had tried flashing WP 7 more than once, and until now i get this error
On My notebook :
An error has occurred
Read below for more information
Error Description: send d000ff partition data failed
Info: .\RSPL\RSPL.cpp (1279)
Error Description:
Info: .\RSPL\RSPL.cpp (956)
And on my HD2 unit, the messages are :
USB Flasher Mode
Wait USB...USB
Layout...PC=8, ASI=4, OASI=-1
Erase
[ASIZE] START" 365 END: FC0 SIZE: C5B
PARTITION LAYOUT NEW
0: 0219 02A9 10 25
1: 02A9 0319 10 25
2: 0319 0359 10 25
3: 0359 0365 10 25
4: 0365 0FC0 10 25
5: 0FC0 0FC8 10 25
6: 0FC8 0FCC 10 25
7: 0FCC 1000 10 25
Erase...
D S: 0 E: 219
D S: 1 E: 2A9
D S: 2 E: 319
D S: 3 E: 359
D S: 4 E: 365
D S: 5 E: FC0
D S: 6 E: FC8
D S: 7 E: FCC
Save EMBR...
Default OS is WPH NAND...
Flashing 0 partition...0 [219-2A9] M0 OK A23E 288
Flashing 0 partition...0 [2A9-319] M0 OK BC51 2F1
Empty 2 Partition...OK
Flashing 3 Partiotion...3 [359-365] M0 OK D840 361
Flashing 4 Partiotion...4 [365-FC0] M2
And it stoped..
I had search everywhere and i found some thread that write about the error, but when i follow the instruction it didn't work.
So what should i do ?
Thanks,
Ronald
did you tried with "use last 24 partition block" under services in MAGDLR ?
Just something what pops in my head
assangflexx said:
did you tried with "use last 24 partition block" under services in MAGDLR ?
Just something what pops in my head
Click to expand...
Click to collapse
Yup, Including that one & didn't work
Also i Had tried Format the SD from my notebook but still, it didn't work
Additional information : I Use 4Gb MicroSd
Thanks,
Ronald
I'd try with another SD card before anything else. Or if you can try installing without an SD card. I am not sure that this is possible with mango though, but older versions could be installed without an SD card. Just to see if it is causing the problem.
ikovac said:
I'd try with another SD card before anything else. Or if you can try installing without an SD card. I am not sure that this is possible with mango though, but older versions could be installed without an SD card. Just to see if it is causing the problem.
Click to expand...
Click to collapse
This error happened when i use HD2O but didn't happen when i use XBMOD-Yuki ROM
What should i do ?
thanks
ronald_delgeano said:
This error happened when i use HD2O but didn't happen when i use XBMOD-Yuki ROM
What should i do ?
thanks
Click to expand...
Click to collapse
Did you try 'clear SD MBR' in Magldr?
mementototem said:
Did you try 'clear SD MBR' in Magldr?
Click to expand...
Click to collapse
I did that too and still got the error
thanks for replying,
Ronald
I found this thread interesting, for various reason, still a open question and google put it in the front line.
when this error apears in mi HTC HD2 was for a bad flash when i tried the windows mobile 7.8 (problems with the drivers on my windows 7 desktop or garbage in the nand i dont know).
so i tried reflash and always with maldrg 1.13 and a ROM, file and fail.
do the 24mB nand trick and clean SD card and still failing
do a task29 clean and still failing.
change SD and still the failing
and always maldrg put me the warning htc hd2 fatal hit 3 when i do the hardware reset
so my problems was solved with a SD ROM loading trick (load the ROM via microSDcard) with a important warning, do that cleaning ROM with the STOCK MANUFACTURING ROM ( if your cellphone was a telstra reload the telstra ROM with the SD trick, if your phone was vodafone reload the vodafone ROM with te SD trick, if your phone was a T.mobile reload the tmobile ROM with the SD trick etc.....) why, well it will clean all the NAND, including HSPL and the Radio version, and return to windows mobile 6.5 again. to restart and reload windows 7.8 mobile again and it works great.
so problem solved
Hi,
if you have the Huawei U8800 Pro (alias Ideos X5 Pro or U8800+) please try if your smartphone is affected by the sdcard mount bug.
Be sure that you have disabled the "Fast boot" on Settings->Applications->Fast boot (needs to be unchecked).
Then shutdown your U8800Pro and powen on.
Question: Is your sdcard (the external one microsd) correctly mounted? Can you see its content?
If you want your smartphone reads again your sdcard, you need to Reboot and magically Android mounts correctly your external microsd.
Please vote the poll upon this thread!
Regards,
kalo86
While it's unlikely I'll be able to help (the kernel patches I've written in the past have been basic), you should run "dmesg" right after it happens and paste the log here
Thanks qwerty12,
I'm going to post the result.
Be right back,
regards
This is the output of "dmesg": http://pastebin.com/GBWnecwJ
Please try more than one time because the bug is not "regular", it is a sort of random.
But in most cases, about 90%, every power on (after a full shutdown) the external sdcard is not correctly mounted and sometimes Android adverts me in the status bar that the file system is unknown.
Regards
I have 3 different microsd cards:
- Transcend 1GB (no class on the sdcard but > 4);
- Sandisk 4GB class 2;
- Sandisk 16GB class 4.
I have this bug with Sandisk sdcards and NOT with the Transcend one.
I am understanding that our Huawei U8800 Pro wants fast sdcards and my theory is confirmed by several tests.
The Transcend sdcard is the most fast among my sdcards (anyway I don't know the class because it's now written on the sdcard) and I proved its performance with a benchmark software. Its performance are better than Sandisk class 4, then its class is maybe 6.
Regards
Maybe a solution?
Hello dear Forum users,
I finally tried a new way for fixing the sdcard mounting problem.
I am used to format sdcard or any king of external drive with the built in format-tool of Windows 7 x64.
Anyway today I tried a new format tool (of course a new format tool for me ), developed by Panasonic, this is the download link:
https://www.sdcard.org/downloads/formatter_3/sdfmt3_1.zip
I formatted my sdcard with this software and magically the external sdcard is always correctly mounted!
Hoping to help other user,
best regards,
kalo86
Too good to be true i tried this method, has no effect at all..i have tried 2 different cards, class 4 and 6, i guess this bug lives in base huawei 2.3 code.. lets wait for new release from Huawei next week and hope this issue to be fixed.
kalo86 said:
Hello dear Forum users,
I finally tried a new way for fixing the sdcard mounting problem.
I am used to format sdcard or any king of external drive with the built in format-tool of Windows 7 x64.
Anyway today I tried a new format tool (of course a new format tool for me ), developed by Panasonic, this is the download link:
https://www.sdcard.org/downloads/formatter_3/sdfmt3_1.zip
I formatted my sdcard with this software and magically the external sdcard is always correctly mounted!
Hoping to help other user,
best regards,
kalo86
Click to expand...
Click to collapse
Oh, I'm very sorry to hear this
Anyway I changed something on the init.rc file (on the ramdisk of the kernel), so I don't know if the solution is a combination of the init.rc and sd-format tool. What I know is that my combination solved my drastic problem. Watching the status of the poll I have to say that there is for sure a problem on the huawei 2.3.5 base, yes, you're right.
If you want you can try my boot.img, based on genokolar kernel but I deleted lots of script, it's very "light" and like the stock one, except for the root rights.
Moved To Q&A
We now have a Q&A section. Please post all questions there
Download any Linux distribution and open a virtual terminal or terminal. Then do next things on bash:
1. Log in as root with su program by typing "su" and give root password (check distributor help page what is root in Live mode if using such).
2. Use dmesg and tail programs to get device information by typing
"dmesg | tail"
3. Physically connect your MicroSD card to reader
4. Re-use dmesg and tail programs to get device information of connected MicroSD by typing
"dmesg | tail"
5. Read what device was connected (Example /dev/sdb (! Not /dev/sdb1 or anything else number, just /dev/sdX)) from the output what dmesg program gave you when connected the MicroSD card
6. Overwrite whole card with full of zeroes with dd program and zero generator by typing
"dd if=/dev/zero of=/dev/sdX"
!!! IT WILL DESTROY ALL DATA ON CARD AND PARTITION TABLE !!!
and just wait that dd program write the whole card full of zeroes. of= means "Output File" and if= means "Input File". Be very careful that you have correct MicroSD card targeted (of=).
7. After you have cleared the whole card, eject it from card reader and re-insert it.
8. Re-use dmesg and tail programs to confirm the same device file is used
9. use fdisk program to create a new partitions and partition table to the card by typing
"fdisk /dev/sdX"
and press m for help. You need to create a new primary partition (n) and then write it to disk and quit (w). You can print already existing partitions with p as Print.
10. Eject the card and re-insert it
11. Use again dmesg and tail program to confirm new device files and partitions (Example, now there should be /dev/sdb, /dev/sdb1 if created one partition)
12. Generate a filesystem on created partitions and write them to partition table with filesystem tools (fat32 filesystem usually is wanted) by using mkfs.vfat program.
Type "mkfs.vfat /dev/sdX1"
13. Eject and re-insert the card
It should now be working again, with FAT32 partition on it.
P.S You can skip 7-13 parts if you want to do partitions on Windows, I always do it on Unix because Windows might get things still wrong but after the partition table is re-created on Unix, it works on Windows as well.
I have fixed dozens of "broken" cards and sticks by this way.
If you can not get your card listed with dmesg program then that card is physically broken, NAND chip is gone gaga or your card reader is broken as computer does not even recognize the card at all.
Hi Fri13,
Thank you for your post but I have to say that my sdcard (the latest one) was a new one and I bought a new sdcard because I thought that my previous sdcard was broken.
A new sdcard cannot get the same problem.
This is a bug!
Hi
I was gonne try formatting the SD card with the program you recommended and changing the boot.img. But if i use youre boot.img does that mean i cant use a custom ROM? Just before i got the problem i was thinking about using one.... Now to the formatting program xD it is 3 options i can choose between in the program which one is the one that im supposed to use? i can choose between: Quick, Full (Erase) and Full (Overwrite). Which one is it?
theminikiller said:
Hi
I was gonne try formatting the SD card with the program you recommended and changing the boot.img. But if i use youre boot.img does that mean i cant use a custom ROM? Just before i got the problem i was thinking about using one.... Now to the formatting program xD it is 3 options i can choose between in the program which one is the one that im supposed to use? i can choose between: Quick, Full (Erase) and Full (Overwrite). Which one is it?
Click to expand...
Click to collapse
Hi theminikiller,
If I'm not wrong you have the U8800 which has a different boot.img (kernel of U8800 pro version).
Then you can only try formatting the external sdcard.
Open SDFormatter;
Click on Option;
Format type ---> Quick
Format Size Adjustment ---> ON
I used these settings.
Regards,
kalo86
I tryed to format my sd-card but after i formatted it, copyed back everything i had on it and put it back in my phone it tells me up in the notification bar that the SD-card is damaged. Shouldnt i have copyed back the things i had on it before? or was it something else that went wrong?
I'm not sure, if this topic has been posted earlier. I tried searching on XDA for a solution for this and couldn't find any!
Problem started when i updated (thru OTG) the device to 6.0.1 (stock), the device was fine that day and after i restarted my phone, it showed "Corrupted SD Card" msg. I tried formatting it as Internal Storage and couldn't succeed (The partition error started popping up!).
Sriram7 said:
I'm not sure, if this topic has been posted earlier. I tried searching on XDA for a solution for this and couldn't find any!
Problem started when i updated (thru OTG) the device to 6.0.1 (stock), the device was fine that day and after i restarted my phone, it showed "Corrupted SD Card" msg. I tried formatting it as Internal Storage and couldn't succeed (The partition error started popping up!).
Click to expand...
Click to collapse
SD card corrupted and not recognized? Same where with two SD cards....Must be a software issue...My problem occured during flashing cm13 with apps by adb sideload - basicly via USB....The card is fine and the SD slot seems to be fine but somthing is not due to this error.
Some times it could be a hardware issue.. I lost my sdcard slot
b00tbu9 said:
Some times it could be a hardware issue.. I lost my sdcard slot
Click to expand...
Click to collapse
Could be however the sd card is being recognized as broken....so the signal that there is a sd card is made....i think it's a software issue....something is screwed up. Will looke into it later .
I have a problem with a new SD card on a new Galaxy S8. It worked perfectly for 5 days. Then yesterday, I got the error that the card was unsupported. Attempt to format gave me:
command '12 volume partition disk:179,0 public' failed with '400 19 command failed" at 20%. No updates were involved.
Anyone else have this problem? Did the phone cause the corruption of the card? Also, the phone tends to run a bit hot even after closing apps.