Database Users

[Q] Cannot Format /Data

Whenever I try to format /data through CWM 3.0.2.8, it returns the message.
error while formatting /data
Click to expand...
Click to collapse
Also when I try to restore a backup, CWM cannot format /data.
I've also tried to install CM7. It says it completed its install in CWM but when I reboot, it retains the OS (rooted stock 1.2) I was currently on.

Me too. I just updated to MR1 and I am trying to restore the /data directory and I can't.

There's one thing I noticed about this refurb'd nook color. The space available in the device info is 1GB. Shouldn't it be higher or did they change the file structure with the latest models?
Also, I went into ADB and mounted EMMC. The last modified date for the files in there is May 4th.
Edit
Not sure if this would help.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LB
A)
~ #
Click to expand...
Click to collapse
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7937MB 7477MB extended
5 461MB 938MB 477MB logical ext2
6 938MB 6490MB 5552MB logical ext3
7 6490MB 6860MB 370MB logical ext3
8 6860MB 7937MB 1077MB logical fat32 lba
(parted)
Click to expand...
Click to collapse

Someone responded back to me on this forum.
http://androidforums.com/b-n-nookcolor/333668-format-internal-partition.html#post2672750
Barnes & Noble has started shipping new NOOK Color devices that are partitioned to allow only 1 GB of "user sideloaded" storage. The remaining 7 GB are partitioned for the OS, apps from the new B&N Apps store, and items downloaded directly from B&N. For the typical (non-rooted) device, the user would have to use the microSD slot for additional storage. I suspect you got one of the newly partitioned devices, which is why you are now seeing only 1 GB instead of the previous 5 GB of storage available.
Click to expand...
Click to collapse
Is there anyway to repartition the new devices or I'm stuck with this? If not, it's going to prevent me from dualbooting. This might also be the cause of my second problem, installing CM7 and still ending up with the original OS.

Oh man am I glad I found this thread. I was freakin' out when I couldn't load phiremod onto my newly purchased NC. Turns out I can only see 1GB of storage like the others in this thread. Hopefully some one will find a way to repartition the newer devices otherwise I am stuck with a rooted NC running the stock ROM with no way to return it.

You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.

jb7038 said:
You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.
Click to expand...
Click to collapse
Trying to load new ROMS fails because I can't do a data wipe as instructed.

I wonder if they made it so that outside sources can't write or modify /data now but it's still rootable with manualnooter.. I can format the other partitions through CWM and restore them easily.
EDIT
http://www.barnesandnoble.com/nookcolor/features/index.asp?cds2Pid=35583
*1GB = 1 billion bytes; Actual formatted capacity may be less. Approximately 5GB available to store content, of which up to 4GB may be reserved for content purchased from the Barnes & Noble NOOK Store.

I am not sure what kind of security they could have on the actual partitions, but the dual boot ROMS show that resizing the partitions should not be to hard, though it does mean you may lose data (possibly).

I don't mind losing my /data. I rather be able to install CM7 or something on the EMMC as opposed to running it on the SD.
I'd be grateful if someone could show me how to partition it so it's back to the original partition, 4gb/4gb as opposed to 7gb/1gb I think.

I hope something is figured out soon.

Here's the solution to anyone following this thread.
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110

I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....

Sparks1641 said:
I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....
Click to expand...
Click to collapse
I did this too and it scared the crap out of me when it kicked me out of fdisk. I thought I hosed it for good. Then when I did the 8 resets it kept going into CWM on the 8th reset. It wasn't until I rebooted it from CWM did it go and reflash itself.
Man that was scary. I thought I had a $250 paper weight.

I was a little freaked out when the fdisk said it didn't work... But reading around I seen that its almost impossible to break it as long as you don't mess with the first 3 partitions so what was the worse case I figured... This must be an issue with the CWR though.. Probably just updating the CWR to format different sizes of the partitions... A format with offset and length feature in an advanced menu... then we can change the sizes to what we want.. But going forward until CWR gets updated every new nook probably gonna have to do the partition change... Not like that's a big deal...

I bought a Nook Color used off craigslist cus they "bricked" it. I thought, no prob, through in the CWM uSD card, erase the data and system, and throw 1.2 on to root.
Can't erase the Data!
They said it was only a few weeks old. I'm guessing it was a refurb with new partition, they tried to root it somehow, and messed it up, then gave up.
Let's hope this fixes it!

Let us know if the partition thing works.. that would be cool.. GL.....

Sparks1641 said:
Let us know if the partition thing works.. that would be cool.. GL.....
Click to expand...
Click to collapse
I did the repartition here:
http://forum.xda-developers.com/showthread.php?t=1094371
and it worked like a charm - finally have CM7 on my 4th Nook!
Thanks to DeanGibson.

URGENT! Help Needed - phone may be bricked, not sure what to do

Hello everyone,
I have a Desire HD (Telus) rooted with Android Revolution 5.2.6 installed and 4ext recovery mod.
Overnight my phone locked up and then after popping the battery I could get maybe 30 seconds of use before it would crawl to a halt and lock up again.
I decided to try to wipe the phone and reinstall. Except all of the processes don't complete now. I'll either get (Error 1) or (Error 255) when trying to use the SuperWipe, install the ROM or use the "Wipe all partitions" option.
Right now it's in the 4ext recovery mod and since I've tried all of the wipe options is it safe to try to reboot (back into recovery) or have I wiped 4ext off as well? I have googled this and can't find an answer.
I've noticed that there is a new version of 4ext available (I have 4.1.3 RC2) but apparently the only way to update is via the app store - which obviously I can't do right now.
When trying to format system partition the screen goes blank for a few minutes and eventually returns to the main menu with no info other than a bunch of "E: Can't mount /cache/recovery" messages. The partition list shows system/data/cache as ext4 with only "iB" in the free column.
I'm not sure what to do. Can anyone offer some suggestions?
Here are some recovery log snips:
Code:
==============================================
| Wiping Script |
| This operation will remove all your data |
| You have 10 seconds to remove the battery |
| to cancel this procedure |
==============================================
unmount of /cache failed; no such volume
about to run program [/sbin/erase_image] with 2 args
1. Erasing & formatting EXT4 *CACHE* partitionCreating filesystem with parameters:
Size: 314572288
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1200
Label:
Blocks: 76799
Block groups: 3
Reserved block group size: 23
Created filesystem with 11/19200 inodes and 2459/76799 blocks
(cache is unmounted already)
error: file_write: write: I/O error
E:Error in /sdcard/Android_Revolution_HD_Super_Wipe.zip
(Status 1)
Installation aborted.
MD5s are valid for the super wipe and the new rom:
Code:
Checking md5sum..
md5sum for this file:
89ad0a12c631e28d34d24ee3ea3d64c8
Checking md5sum..
md5sum for this file:
59531c9715527f5725cbd716dfae4549
Here's what happens when I try to flash the ROM:
Code:
===============================================
| Android Revolution HD |
Creating filesystem with parameters:
Size: 585104896
Block size: 4096
Blocks per group: 32768
Inodes per group: 7143
Inode size: 256
Journal blocks: 2232
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35715 inodes and 4603/142847 blocks
| by mike1986 |
| Be patient - 1st boot may take a while |
===============================================
>>> Formatting partitions
error: file_write: write: I/O error
E:Error in /sdcard/Android_Revolution_HD-4G_5.2.6.zip
(Status 1)
Installation aborted.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:Can't unlink /cache/recovery/command
-- Formatting boot...
Formatting /boot...
I:Formatting unknown device.
-- Formatting system...
Formatting /system...
Creating filesystem with parameters:
Size: 585104896
Block size: 4096
Blocks per group: 32768
Inodes per group: 7143
Inode size: 256
Journal blocks: 2232
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35715 inodes and 4603/142847 blocks
error: file_write: write: I/O error

This is out of my league really technically. Is the rom zip OK? I see the error starts with that file. If all else fails I would try to put another rom file onto the SD Card and flash that in case it's just a bad file. (or bad SD Card)
In my experience I've only ever done any or all of the following:
wipe data/factory reset
wipe cache
wipe dalvik cache
wipe battery stats
format system
format data
(I've never done or wiped or formatted anything else.)
Hopefully a more technically experienced person can help.
I'm really uncomfortable formatting partitions, so I never touch them. I'm not sure of the state of yours. You could try to flash the smallest rom file you can. ie. the smallest rom zip size.

Thanks for the reply - I did upload another ROM and it failed in the same way. The logs are clearly indicating something wrong with the Flash filesystem on the device.
I don't know if I can shut down to swap the card and boot back into the 4EXT recovery - does "Wipe all partitions" remove 4EXT as well?

I have tried formatting partitions as EXT3 as well and no dice - here's the recovery log:
Code:
Formatting /system...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: 256-byte inodes not usable on older systems
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
/sbin/tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p25
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
Formatting system completed.
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: 256-byte inodes not usable on older systems
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
/sbin/tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p26
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
Formatting data completed.
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
Formatting cache completed.
partition | fs | capacity | free
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
df: /system: can't find mount point
umount: can't umount /system: Invalid argument
system ext3 558 MiB iB
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
df: /data: can't find mount point
umount: can't umount /data: Invalid argument
data ext3 1175 MiB iB
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Invalid argument
df: /cache: can't find mount point
cache ext3 300 MiB iB
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: Device or resource busy
sdcard fat32 1945 MiB 1.3GiB

I use amon ra recovery but it seems to me that your partition is somehow damaged, you should copy everything thats on ur sd card onto your computer and try formatting the sd card on the computer, see if that reformats the entire sd card and gets rid of the ext4 partition. If it does, then copy the recovery zip on there and try to reflash the recovery. Then try to repartition.
Sent from my PC36100 using xda premium

Synergies14 said:
I use amon ra recovery but it seems to me that your partition is somehow damaged, you should copy everything thats on ur sd card onto your computer and try formatting the sd card on the computer, see if that reformats the entire sd card and gets rid of the ext4 partition. If it does, then copy the recovery zip on there and try to reflash the recovery. Then try to repartition.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. The problem isn't the SD card itself it's the internal flash memory. 4EXT can read and calculate the correct MD5 sums of the images on the SD card. It fails when trying to format the internal flash.

Telek said:
Thanks for the reply. The problem isn't the SD card itself it's the internal flash memory. 4EXT can read and calculate the correct MD5 sums of the images on the SD card. It fails when trying to format the internal flash.
Click to expand...
Click to collapse
Is there a way you can remove your sdcard and then boot into recovery and try to do a factory reset/restore?, maybe try flashing a stock rom. I know this may not be abit of help but i would like to try and think of all possible things to do.

Synergies14 said:
Is there a way you can remove your sdcard and then boot into recovery and try to do a factory reset/restore?, maybe try flashing a stock rom. I know this may not be abit of help but i would like to try and think of all possible things to do.
Click to expand...
Click to collapse
I've tried the factory reset/restore and it didn't work. I'm worried about powering off right now because I don't know enough about how recovery is setup. Since all partitions have been wiped will I be able to boot back into 4EXT recovery?

Edit: thought you had a Desire not a desire hd, sorry

Telek said:
I've tried the factory reset/restore and it didn't work. I'm worried about powering off right now because I don't know enough about how recovery is setup. Since all partitions have been wiped will I be able to boot back into 4EXT recovery?
Click to expand...
Click to collapse
try downloading a stock released rom, not a custom rom and rename it to pd98img.zip and place it on your sd card. turn off your phone and go into the bootloader menu and it should auto detect the pd98img.zip file and it will ask you if you want to update. Choose yes and see if it installs. Thats installs the rom bypassing the recovery mod telling it to install on the partition.

madmaxx82 said:
Edit: thought you had a Desire not a desire hd, sorry
Click to expand...
Click to collapse
The ext3 format was a desperate attempt to get something to work. The installer before (check the top logs) was formatting as ext4.
I currently have 4.1.3 RC2 installed.
Synergies14 said:
try downloading a stock released rom, not a custom rom and rename it to pd98img.zip and place it on your sd card. turn off your phone and go into the bootloader menu and it should auto detect the pd98img.zip file and it will ask you if you want to update. Choose yes and see if it installs. Thats installs the rom bypassing the recovery mod telling it to install on the partition.
Click to expand...
Click to collapse
OK I'll give that a try. I have the PD98IMG.zip file from when I rooted my phone - that should work?

Telek said:
The ext3 format was a desperate attempt to get something to work. The installer before (check the top logs) was formatting as ext4.
I currently have 4.1.3 RC2 installed.
OK I'll give that a try. I have the PD98IMG.zip file from when I rooted my phone - that should work?
Click to expand...
Click to collapse
I got a shock when I saw ext3 since you had posted in the Desire forum's 4ext thread! The Desire has yaffs2 partitions after all
I really hope you get your phone working after flashing the ruu!

Telek said:
OK I'll give that a try. I have the PD98IMG.zip file from when I rooted my phone - that should work?
Click to expand...
Click to collapse
I'm not exactly sure. You can take anything and rename it as PD98IMG.zip and flash it. Chances are, the file you have is the recovery program. Im not sure where you can get a stock rom for your phone at. but if you find one, make sure its legit and the download is correct and use the method i mentioned. Let us know what happens.

madmaxx82 said:
I got a shock when I saw ext3 since you had posted in the Desire forum's 4ext thread! The Desire has yaffs2 partitions after all
I really hope you get your phone working after flashing the ruu!
Click to expand...
Click to collapse
Yeah my bad - I didn't even notice it was the wrong thread.
Ok so is there a PB99IMG.zip that will work for the Desire HD?

Telek said:
Yeah my bad - I didn't even notice it was the wrong thread.
Ok so is there a PB99IMG.zip that will work for the Desire HD?
Click to expand...
Click to collapse
NP
Is there no shipped roms thread for the Desire HD? Get an official RUU like Synergies14 suggested
---------- Post added at 05:29 AM ---------- Previous post was at 05:17 AM ----------
If you want I can package you a recovery you can flash from inside recovery.
I said it wasn't possible because I thought you had a desire. Now that this has changed it's no problem.
But I really don't think it could solve the problem.
Maybe the best would be to really flash an official ruu so you know if your device is ok or not ok.
If the ruu doesn't boot/flashing fails (not because of cid errors, but during flashing), then you really should send it in..

madmaxx82 said:
NP
Is there no shipped roms thread for the Desire HD? Get an official RUU like Synergies14 suggested
---------- Post added at 05:29 AM ---------- Previous post was at 05:17 AM ----------
If you want I can package you a recovery you can flash from inside recovery.
I said it wasn't possible because I thought you had a desire. Now that this has changed it's no problem.
But I really don't think it could solve the problem.
Maybe the best would be to really flash an official ruu so you know if your device is ok or not ok.
If the ruu doesn't boot/flashing fails (not because of cid errors, but during flashing), then you really should send it in..
Click to expand...
Click to collapse
I agree - I'm trying to find a stock ROM.
Does this one look good?
http://forum.xda-developers.com/showthread.php?t=1145397&page=2
I don't know what ACE means.

Telek said:
I agree - I'm trying to find a stock ROM.
Does this one look good?
http://forum.xda-developers.com/showthread.php?t=1145397&page=2
I don't know what ACE means.
Click to expand...
Click to collapse
BTW: How did you get s-off?
Do you have supercid?
I'm not so familiar with the desire hd I must admit.
---------- Post added at 05:33 AM ---------- Previous post was at 05:32 AM ----------
Ace is the name of the Desire HD.

madmaxx82 said:
BTW: How did you get s-off?
Do you have supercid?
Click to expand...
Click to collapse
The one I just linked is
RUU_Ace_Gingerbread_S_TELUS_WWE_2.43.661.1_R_Radio _12.56.60.25_26.10.04.03_M
I should be able flash that and then go back to Revolution?
I followed these guides to root and s-off. I think I supercid'd as well but honestly can't remember. How do I check?
http://www.addictivetips.com/mobile/how-to-root-telus-htc-desire-hd/
EDIT: Yes, I believe that does SuperCID as well.

Telek said:
The one I just linked is
RUU_Ace_Gingerbread_S_TELUS_WWE_2.43.661.1_R_Radio _12.56.60.25_26.10.04.03_M
I should be able flash that and then go back to Revolution?
I followed these guides to root and s-off. I think I supercid'd as well but honestly can't remember. How do I check?
http://www.addictivetips.com/mobile/how-to-root-telus-htc-desire-hd/
EDIT: Yes, I believe that does SuperCID as well.
Click to expand...
Click to collapse
Oh I see so you really have telus desire hd I suppose?
Then I think you should just use the rom zip linked in the rooting guide again.

madmaxx82 said:
Oh I see so you really have telus desire hd I suppose?
Then I think you should just use the rom zip linked in the rooting guide again.
Click to expand...
Click to collapse
Yes I do have Telus DHD - and I was just posting that I was going to use that ROM from the rooting guide since I'll have to use it again anyway in order to re-root my phone
Is it possible to make a PB99IMG.zip with the latest 4EXT before I go this route? I'd rather give that one quick try before I have to re-root the phone.
Thanks!

[Q]help i soft bricked my phone

hi guys i am in a big mess
1)i tried installing official 2.3.5 final and my phone(u8800) started bootlopping after factory reset i managed to start it once.
2)i restarted my phone after rooting it and had again bootloops that i didnt ever manage to overcome.
3)so i desided that i should reflash official(and the desaster started)update failed on 99% and the worst bootloader locked .
4)i tried installing an official froyo also failed at 99% but bootloader unlocked
5)now i am on ubuntu able to see pink screen files but unfortunately i dont have dd back up but i have many back ups from cwm on my sd from custom roms is there any posibility to unbrick my phone?
ps for admin sorry for same thread but the other started writing in some unknown language to me

Can you access recovery?
So you downgraded to 2.2, which version B138?
can you try to access recovery? official will do for factory reset, if doesn't start again try to flash it again, and after that do wipe and factory reset from recocery...
I managed to downgrade like that also failed at 99% but with factory reset the phone started normally...

Atanasov Goran said:
So you downgraded to 2.2, which version B138?
can you try to access recovery? official will do for factory reset, if doesn't start again try to flash it again, and after that do wipe and factory reset from recocery...
I managed to downgrade like that also failed at 99% but with factory reset the phone started normally...
Click to expand...
Click to collapse
1)yes my 2.2 froyo is 138 from how to root ginerbred thread and after this flash i lost adb compatibility in windows so now i am in ground zero if ther is a way to flash something from ubuntu or backtrack in bootloader mode because even after that still no access to phone not even from pc on cwm to see my sd card
2)in simple boot my phone stacks on huawei logo,i can also get to recovery menu and finaly and i think the most helpfull i can get pink screen and mount my files on linux.
3)i have also try to recover in last saved working recovery (custom rom)
4)i think that something went wrong with my partitions but i realy need help from a developer because i dont know what to do

try this
try to wipe/factory reset from the official recovery, should start normaly after that, my phone did the same when i downgraded from 2.3 stoped at 99% and said that the update failed but after a factory reset booted normaly

Maybe a partition is damaged.
Try from linux on pink screen to check partitions for errors. Maybe you can fix it like this and after to successfully flash the update.

dancer_69 said:
Maybe a partition is damaged.
Try from linux on pink screen to check partitions for errors. Maybe you can fix it like this and after to successfully flash the update.
Click to expand...
Click to collapse
can you give some info how to do that i see 3 partitions of 105mb,235 and recovery partition only who auto mount and on gparted i see 4gb unreachable
do you mean just to check disk this partitions ?

I haven' t specific infos, I'm using linux very rear the last year. I think that you can use the fsck tool of linux. You can find a lot of info about how to check partitions for linux if you search on google. Just be careful to not format them or erase them.

Tranos said:
can you give some info how to do that i see 3 partitions of 105mb,235 and recovery partition only who auto mount and on gparted i see 4gb unreachable
do you mean just to check disk this partitions ?
Click to expand...
Click to collapse
You should see 13 partitions total if you look at the drive with parted or gparted etc.. And yeah you could run fsck on all the ext3/ext4/fat32 partitions. But if you don't see all the 13 partitions in parted / gparted then I think the partition table is damaged or some weird bootloader lock issue.

after some tries and stock reflashes i am now on official cwm recovery and trying to wipe data/factory resets returns me an error :
E:cant mount @(or /dev/block/mmcblk0p13) both wipe and format same error
can you candly send me the official recovery files and what should i have in(i think something after so many custom roms failed)
and this are the partitions i can see now

You could run gparted and note down all partitions which are ext3, ext4 or fat32. Then you can check the disks with "sudo fsck /dev/sdxx". Also I can post my partition table later when I'm on my comp so you could compare it to yours.
Sent from my u8800 using xda premium

thies are all partitions but i think there are too many anallocated
Code:
GNU Parted 2.3
Using /dev/sdd
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Error: Invalid partition table on /dev/sdd -- wrong signature 0.
Ignore/Cancel? i
Model: Qualcomm MMC Storage (scsi)
Disk /dev/sdd: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 252MB 252MB primary fat32
2 252MB 252MB 512kB primary boot
3 252MB 255MB 3072kB primary
4 255MB 3959MB 3704MB extended
5 268MB 281MB 12,6MB logical
6 336MB 472MB 136MB logical ext3
7 537MB 537MB 512kB logical
8 604MB 607MB 3146kB logical
9 671MB 678MB 7168kB logical
10 738MB 741MB 3146kB logical
11 805MB 808MB 3146kB logical
12 872MB 1103MB 231MB logical ext3
(parted)
2 partitions are missing

Here's how mine looks. I'm guessing you don't have a dd backup of the whole phone? Anyway if your partition table is messed up, it would be possible to clone my partition table. Only the partition table, and leaving all other data intact. It would probably be a good idea also to check with others if the partition table is always exactly the same on all phones, or if there are different flash mems or something with diff. tables. Also did you run fsck on 1,6,12 and 13?
Code:
$ [B]sudo parted /dev/sdc[/B]
GNU Parted 2.3
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) [B]p[/B]
Model: Huawei eMMC Storage (scsi)
Disk /dev/sdc: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 252MB 252MB primary fat32
2 252MB 252MB 512kB primary boot
3 252MB 255MB 3072kB primary
4 255MB 3959MB 3704MB extended
5 268MB 281MB 12.6MB logical
6 336MB 472MB 136MB logical ext4
7 537MB 537MB 512kB logical
8 604MB 607MB 3146kB logical
9 671MB 678MB 7168kB logical
10 738MB 741MB 3146kB logical
11 805MB 808MB 3146kB logical
12 872MB 1103MB 231MB logical ext2
13 1141MB 1770MB 629MB logical ext4
14 1812MB 3959MB 2147MB logical fat32
(parted)

do you know how ican fix my partitions again or should i sent it to service tbh it is huawei fault that my phone doesnt work now

I checked my partition table(I have 2.3 installed, not 2.2) and are same that ksata' s, except partition 12 which is in ext3, not ext2.
But I think that on 2.2 rom the partition table has 12 partitions and not 14(I've used command cat /proc/mounts some times when a was on 2.2 rom and always partitions count was until 12). So, I don' t think that it' s something wrong with the partition table.
But maybe some of the existing partitions is damaged and when update tries to write on it, gets an error and update stops.
You can check the ext2/3/4 partitions from gparted. First umount a partition end then check it(if you right click on a partition these options are available on the menu)

Looks like I have bricked mine too.. pretty badly. When updating to 2.3 if fails at step 2 (40 %) and shows "update failed" (same with 2.2). Can't access recovery either. In pink screen Windows and Ubuntu doesn't mount any partitions..
Looks like I have to send it in to change motherboard, but if any have suggestions how to fix it please tell me
ps. was on Cm7 before this happened.

skifyr123 said:
Looks like I have bricked mine too.. pretty badly. When updating to 2.3 if fails at step 2 (40 %) and shows "update failed" (same with 2.2). Can't access recovery either. In pink screen Windows and Ubuntu doesn't mount any partitions..
Looks like I have to send it in to change motherboard, but if any have suggestions how to fix it please tell me
ps. was on Cm7 before this happened.
Click to expand...
Click to collapse
Try to flash using internal SD card. Also, one user reported that removing battery worked.

Blefish said:
Try to flash using internal SD card. Also, one user reported that removing battery worked.
Click to expand...
Click to collapse
How to access internal when you can't boot (not even to recovery)? Tried to remove battery, but didn't work..

1)i managed to solve my problem by using the genokolars re-partition to stock from modaco and the partition zip that is at a reply of him not post start thank you everybody for the try .and after reflashed the chinese stock 162
2)but now i have nulled imei can i restor it by some clock works recoveries or ther is no way to restore it(i dont have dd back up)

skifyr123 said:
How to access internal when you can't boot (not even to recovery)? Tried to remove battery, but didn't work..
Click to expand...
Click to collapse
Have the same issue. Did you try to work it out somehow?
Try look at my thread here:
http://forum.xda-developers.com/showthread.php?t=1466953

[Q] Partitions missing, need someone like Blefish

After restoring from a cwm backup made on another partition table (that's made by Geno if I remember it correctly) I've got a soft-bricked device (only pink screen, nothing else). Thanks to http://forum.xda-developers.com/showthread.php?t=1541765 I could unbrick it but some bugs appeared: 1) the only ROM that could properly mount internal storage was Aurora (btw, I was on Aurora when phone bricked); 2) the only ROM that had working USB Mass-storage was... Aurora! It was completely messed up on stock roms: when there is no external sd I could turn on USB storage and couldn't turn it off, when external sd is in I couldn't turn on the USB storage, but both internal and external sd were accesible in Windows and the phone displayed that both sd-cards were unsafely dismounted, also they were unaccesible from the phone untill reboot; 3) I had neither IMEI, nor mac adress from there on. Both serial numbers were also missing.
As Aurora is still pretty unstable for daily use for me I prefer to run CM7.2, but installation of CM ended hanging at Huawei logo. I've tried to move back to stock partition table via stock-partition.zip found somewhere there, but now I have no internal storage at all, recovery can't find neither external no internal sd.
SOLVED USING THIS: (http://forum.xda-developers.com/showthread.php?t=1971266)

Try Geno's official partition maybe? This is why a disk IMG is important...
Lo... I need Blefish? This is going to be funny.
Sent from my Impulse 4g using xda premium

Somcom3X said:
Try Geno's official partition maybe? This is why a disk IMG is important...
Lo... I need Blefish? This is going to be funny.
Sent from my Impulse 4g using xda premium
Click to expand...
Click to collapse
Already tried, it gives me my internal storage back, but mass storage mode is still broken.
"Someone like Blefish" -- just because he knows everything about our phone's partitions

nagato.fm said:
Already tried, it gives me my internal storage back, but mass storage mode is still broken.
"Someone like Blefish" -- just because he knows everything about our phone's partitions
Click to expand...
Click to collapse
Try toggling Mtp
Sent from my U8800pro using xda premium

Somcom3X said:
Try toggling Mtp
Sent from my U8800pro using xda premium
Click to expand...
Click to collapse
Mtp is an only-ics feature, isn't it? And my problem is that I can't use froyo and gingerbread roms because of broken mass storage.

Well, I have heard that if you have IMEI 0, you will also have mass storage problems and more. Try to restore your IMEI first. Either use the previously backed up or use the tutorial somewhere around this forum to reenter it.

Blefish said:
Well, I have heard that if you have IMEI 0, you will also have mass storage problems and more. Try to restore your IMEI first. Either use the previously backed up or use the tutorial somewhere around this forum to reenter it.
Click to expand...
Click to collapse
Already tried it, IMEI was restored, but mass storage wasn't working. I tried to restore it when testing mass storage on different ROMs and flashing B138 killed my IMEI again.
Edit:
Disk /dev/sdb: 3959 MB, 3959422976 bytes
1 heads, 62 sectors/track, 124729 cylinders, total 7733248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 491520 245760 b W95 FAT32
/dev/sdb2 * 491521 492520 500 4d QNX4.x
/dev/sdb3 492521 498520 3000 46 Unknown
/dev/sdb4 498521 7733247 3617363+ 5 Extended
/dev/sdb5 524288 548863 12288 59 Unknown
/dev/sdb6 655360 921599 133120 4c Unknown
/dev/sdb7 1048576 1049575 500 5a Unknown
/dev/sdb8 1179648 1185791 3072 58 Unknown
/dev/sdb9 1310720 1324719 7000 50 OnTrack DM
/dev/sdb10 1441792 1447935 3072 4a Unknown
/dev/sdb11 1572864 1579007 3072 4b Unknown
/dev/sdb12 1703936 2154495 225280 83 Linux
/dev/sdb13 2228224 3457023 614400 83 Linux
/dev/sdb14 3538944 7733247 2097152 b W95 FAT32
(I don't simply know why I am putting it here)

Okey, all my problems were solved by the guide mentioned in first post. It seams like I messed up something in the internal memory of phone so after restoring all the memory from a full image all works perfectly.
I'll be more accurate in what I do with phone next time.

nagato.fm said:
Okey, all my problems were solved by the guide mentioned in first post. It seams like I messed up something in the internal memory of phone so after restoring all the memory from a full image all works perfectly.
I'll be more accurate in what I do with phone next time.
Click to expand...
Click to collapse
Your welcome
Sent from my U8800pro using xda premium

CWM cannot restore /system due to no space (ZTE Blade C V807 / V889s)

Hey guys, I was trying to increase app storage by re-partitioning the internal storage with Mt657xRepartition_EN.apk, where I selected 1gb for app storage. The next step was to wipe data/factory reset. Post this step, the phone is stuck at boot logo. So I tried restoring my backup via CWM and it failed while restoring /system. The log reveals that system cannot be restored due to no space left on the partition. As per my understanding, the above repartitioning was for data partition, but it may have messed up something. Here is full log while trying to restore system from advanced restore:
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created file system with 11/32768 inodes and 4206/131072 blocks
SDCardUpdate.apksdcarda7d2cf64.0bouncycastle.odexl ibbinder.solimobilelog_jni.soProcyon.oggOrganDub.o ggtar: write error: No space left on device Vendor_045e_Product_028e.klError while restoring /system!
When connected to MTKDroidTools, the device is recognised in CWM recovery, but the kernel and baseband fields are empty. There is a blue dot at bottom left with some Russian word (see attachment). With MTKDroidTools, I was able to recover block map on the ROM (see attachment) where it says the following: System space is 64,27,77,088 bytes. The recovery on the PC says the system.ext4.tar file is 52,72,86,272 bytes. Therefore it should be able to restore, right? Also, isn't cache a bit too big at 485490688 bytes, which is same as usrdata at 463mb? usrdata was about 463mb before starting this, so that means partitioning failed, right? (I had selected 1 gb for the same).
When backup was made with MTKDroidTools, I found this:
- nodl_pmt
- PMT tables found
- PMT tables OK, 18 blocks found
--- Kernel Block Map to PMT mismatch!
-------------------------------------------
BlockName Offset
-------------------------------------------
Kernel: __NODL_BMTPOOL 0x00000000FFFF00A8
PMT: Not present! ??????????
-------------------------------------------
--- scatter from PMTis write to the file:
E:\Desktop\Android\MTKDroid\backups\ZTE-BLADE-C_130508_backup_140617-053203\MT6577_Android_scatter_emmc_PMT.txt
- Use it if SP FlashTool errors of 8038 or 4050 occurs
Although the backup was successful, it's a backup of dead system.
Other Details:
Note: 1. I am able to restore /data and /cache from CWM recovery. I'm a bit worried to try restoring boot partition
2. Backup was made using Custom CWM recovery made with MTKDroidTools
Device: ZTE Blade C
Processor: MT6577 by Mediatek
Storage: 4gb (about 430 to 460mb was internal storage (apps) and 2.2gb was phone storage (media))
ROM: Official, was rooted with vroot and replaced by SuperSU.
I tried flashing custom rom via spflashtools, but it seems to stay stuck at 0% with word searching below (It does recognize that connected at start). Probably has to do with the fact that the phone cannot connect properly to PC when connected in preloader mode (I have installed preload drivers, but the phones seems to connect and disconnect every second)
I really need to revive this device, preferably with some extra space in usrdata partition, if possible. I have browsed several threads and collected this information based on that. Any pointers, help, information, diagnosis, guidance, steps, etc. would be much appreciated. I'll try my best to find my way to the solution. Please tell me if you need any other info. This device is at the edge of bricking. And I had given this to my dad on Father's Day 2 days back. He wasn't receiving emails due to low storage and I told him I can fix it. It would be terrible if I tell him I killed his phone.
I had created this thread before in XDA Assist, but it was promptly closed saying to proceed to device section. Thanks for consideration to those who read through and did not reply for being unable to help.

msmsmsmsms said:
Hey guys, I was trying to increase app storage by re-partitioning the internal storage with Mt657xRepartition_EN.apk, where I selected 1gb for app storage. The next step was to wipe data/factory reset. Post this step, the phone is stuck at boot logo. So I tried restoring my backup via CWM and it failed while restoring /system. The log reveals that system cannot be restored due to no space left on the partition. As per my understanding, the above repartitioning was for data partition, but it may have messed up something. Here is full log while trying to restore system from advanced restore:
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created file system with 11/32768 inodes and 4206/131072 blocks
SDCardUpdate.apksdcarda7d2cf64.0bouncycastle.odexl ibbinder.solimobilelog_jni.soProcyon.oggOrganDub.o ggtar: write error: No space left on device Vendor_045e_Product_028e.klError while restoring /system!
When connected to MTKDroidTools, the device is recognised in CWM recovery, but the kernel and baseband fields are empty. There is a blue dot at bottom left with some Russian word (see attachment). With MTKDroidTools, I was able to recover block map on the ROM (see attachment) where it says the following: System space is 64,27,77,088 bytes. The recovery on the PC says the system.ext4.tar file is 52,72,86,272 bytes. Therefore it should be able to restore, right? Also, isn't cache a bit too big at 485490688 bytes, which is same as usrdata at 463mb? usrdata was about 463mb before starting this, so that means partitioning failed, right? (I had selected 1 gb for the same).
When backup was made with MTKDroidTools, I found this:
- nodl_pmt
- PMT tables found
- PMT tables OK, 18 blocks found
--- Kernel Block Map to PMT mismatch!
-------------------------------------------
BlockName Offset
-------------------------------------------
Kernel: __NODL_BMTPOOL 0x00000000FFFF00A8
PMT: Not present! ??????????
-------------------------------------------
--- scatter from PMTis write to the file:
E:\Desktop\Android\MTKDroid\backups\ZTE-BLADE-C_130508_backup_140617-053203\MT6577_Android_scatter_emmc_PMT.txt
- Use it if SP FlashTool errors of 8038 or 4050 occurs
Although the backup was successful, it's a backup of dead system.
Other Details:
Note: 1. I am able to restore /data and /cache from CWM recovery. I'm a bit worried to try restoring boot partition
2. Backup was made using Custom CWM recovery made with MTKDroidTools
Device: ZTE Blade C
Processor: MT6577 by Mediatek
Storage: 4gb (about 430 to 460mb was internal storage (apps) and 2.2gb was phone storage (media))
ROM: Official, was rooted with vroot and replaced by SuperSU.
I tried flashing custom rom via spflashtools, but it seems to stay stuck at 0% with word searching below (It does recognize that connected at start). Probably has to do with the fact that the phone cannot connect properly to PC when connected in preloader mode (I have installed preload drivers, but the phones seems to connect and disconnect every second)
I really need to revive this device, preferably with some extra space in usrdata partition, if possible. I have browsed several threads and collected this information based on that. Any pointers, help, information, diagnosis, guidance, steps, etc. would be much appreciated. I'll try my best to find my way to the solution. Please tell me if you need any other info. This device is at the edge of bricking. And I had given this to my dad on Father's Day 2 days back. He wasn't receiving emails due to low storage and I told him I can fix it. It would be terrible if I tell him I killed his phone.
I had created this thread before in XDA Assist, but it was promptly closed saying to proceed to device section. Thanks for consideration to those who read through and did not reply for being unable to help.
Click to expand...
Click to collapse
Hey there, I know it's bit late (i dunno if not too late), currently there are no safe ways to repartition Blade C (i've also tried about year ago with mine... just starting form scratch)
You can always reflash that Blade C (or V889S/v807s) with SP FlashTool and stock 4.1.1 JB (or so). Rom (and scatterloading file) can be downloaded at NeedRom website (need to register first, it's free so don't worry ;] )
One more thing... flashing with this method will recreate partions on your phone yet you'll lose all the data so if u can connect via cwm backup everything you can.
oh. Here's working SP Flash Tool