Develop Bugs

[Q] need help E: error in /sdcard/

Hi ive got s-off rooted htc wilfire s via htc-clip, have flashed romto jikantaru rom
only because cant get cyanogenmod to flash keep getting
E: error in /sdcard/ cm_saga_full - 50.zip
(status 0)
installation aborted
Ive tried about 10 times different rom version from different sites, i ve tried 2 different sd cards ive updated cwm recovery to v5.0.2.6 ive wiped cache, factory reset, davlik cache, even tried installing through rom manager no success same error.
any help be much appreciated, would have posted in developer page but im noob as u can probably tell, and i couldnt find a related answer to this in search that actually fixed or addressed this problem in detail, so like i say any help be much appreciated.

more info
marvel pvt ship s-off rl
hboot- 1.03.0000
radio- 7.46.35.00
cwm recovery v5.0.2.6
tried everything i can find related to error on sdcard, nothing seems to make any difference, and it all seems to be errors for different devices. i know im missing something probably very simple, ive tried cleaning everything and installing zip from sd, nothing seems to workand i know its not a problem with the zip, come up no matter what zip i try. is there a problem with what cwm im running ? or do i need format sd in some way thats not fat32 or some sort of sd-ext thats not ext 3?

Does the sd work when your system is booted? Have you tried to reformat it as fat 32? How's your partition table? Have you tried to mount the sd yourself? Is the fat the first partition of your sd? Is at /dev/block the mmcblk1 partition present? Have you tried creating a new goldcard?
Swyped from my Desire S

Does the sd work when your system is booted? Have you tried to reformat it as fat 32?
yeah sd works when system booted, and have tried two different sd`s one 8gb and other 2gb have tried formatting both fat 32 with nothing else present but the rom file and gapps. Ive tried different partitions 1st primary fat32 1024mb and 2nd primary ext 3 1024,
done the same for 8gb 1st fat32 7gb /2nd ext3 1gb, and also tried just one partition all fat 32 on both cards. Ive tried mounting it my self to no avail and tried a new gold card this morning.
how do i check Is at /dev/block the mmcblk1 partition present?

here`s the recovery log dont know if this help.
Starting recovery on Sun Jan 6 00:00:27 1980
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
CWM-based Recovery v5.0.2.6
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext auto /dev/block/mmcblk0p2 (null)
-- Installing: /sdcard/cm_saga_full-50.zip
mtd: successfully wrote block at c6de400000000
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/cm_saga_full-50.zip
Opening update package...
Installing update...
E:Error in /sdcard/cm_saga_full-50.zip
(Status 0)
Installation aborted.
mtd: successfully wrote block at c6de400000000
I:Set boot command ""

pojomojo said:
here`s the recovery log dont know if this help.
Starting recovery on Sun Jan 6 00:00:27 1980
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
CWM-based Recovery v5.0.2.6
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext auto /dev/block/mmcblk0p2 (null)
-- Installing: /sdcard/cm_saga_full-50.zip
mtd: successfully wrote block at c6de400000000
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/cm_saga_full-50.zip
Opening update package...
Installing update...
E:Error in /sdcard/cm_saga_full-50.zip
(Status 0)
Installation aborted.
mtd: successfully wrote block at c6de400000000
I:Set boot command ""
Click to expand...
Click to collapse
Ok, your sd is there (it's mmcblk0 not 1 Sry, confirmed it by looking at the mount output of my girlfriends phone, thought the partitions are named the same way as mine, but they are different).
Did you try to download the package or where did you get it from? I'm just wondering cause the name of your zip is different than the one you can download from the cyanogen thread. And it finds the package, it also tries to apply it, but aborts it cause the package is corrupted or made for a different device.
Swyped from my Desire S

yeah i got cyanogen on it now, seems to be problem with the package i had to use the original package from the first post by alquez
[DEV] Unofficial CM7 PORT - [2.3.7 BETA 1 RELEASE]
and get the first zip : update-cm-7.1.0-BETA1-marvel-KANG-signed.zip
nothing else seemed to work, probably because i was using the nightly for desire s. cheers for ur relpy and help thnx.

sounds kinda like the problem I am having. Look at this shot.

Yeah yours is status 7 error mine was 0, make sure u wipe all cache and davlik and mount storage. Worked for me eventually.

I've done all of that. Just didn't wipe the boot in mounts and storage. I've installed other roms before but this one is giving me the cold shoulder!!!

Your flashing a saga rom which means its for desire s. You cant do that unless you want a bricked phone.

yeah think u need the new cwm recovery now that ive had a look at ur pic on pc, is the old recovery you have.

I have this problem with a Galaxy S2 T-Mobile. Newest Recovery. Except, mine says (Status 1).

sdcard error 0
I have the same error while trying to install a UOT Kitchen zip. I installed it once but can not install a new one.I've wiped cache and dalvik cache. No matter how many times I try to flash it, it keeps aborting. I'm new to this, so if someone can help me please, I would be forever greatful. I have a HTC Wildfire S.

If it worked once r u sure the zip is ok? try download it again.
Sent from my Wildfire S A510e using xda app-developers app

error
yeah, I've downloaded several thinking the same thing to no avail. I've to troubleshoot it issue as much as possible. And I still can't seem to figure it out. If anybody has any other suggestions, that would be great. I've got my phone s-off, rooted with cwm as well.

AdrenalWolfe said:
yeah, I've downloaded several thinking the same thing to no avail. I've to troubleshoot it issue as much as possible. And I still can't seem to figure it out. If anybody has any other suggestions, that would be great. I've got my phone s-off, rooted with cwm as well.
Click to expand...
Click to collapse
quite a strange issue considering u've tried several of the same zip, have u tried a different recovery/cwm?
what does windows say if u open it with 7zip and check the archive? have u tried repacking it?
failing that post to the dev of the thread where u got uot.
best of luck im out of suggestions never used uot kitchen.

[Q] Error formatting /data! Error formatting /cache!

Using CWM 5.0.2.0, when I try to format /data, I get:
Error formatting /data!
When I try to format /cache, I get:
Error formatting /cache!
This all started because I decided to try Albinoman's AOSP 4.2 ROM. This is what happened:
1. Booted into CWM 5.0.2.0, made a nandroid backup of stock GB ROM.
2. Installed Albinoman's ROM using CWM, wiped /cache and /data.
3. Booted Albinoman's ROM, no problems. Decided I wanted to backup and restore some apps in the old ROM using Titanium Backup.
4. Restored nandroid backup of stock ROM. When it rebooted, all was well.
5. Used Titanium Backup to back up my apps.
6. Installed Albinoman's ROM again.
7. Cleared /data, it was fine. Cleared /cache. Stuck at "formatting" for half an hour.
8. Rebooted back to recovery and tried it again. Couldn't find E:.
9. Tried letting it boot. Stuck on the boot animation for 30-minutes.
10. Wipe everything and re-flash. Tried again. Still stuck on boot animation.
11. Manually unmount and tried to format /data and /cache, and I get the error messages.
I had installed Convert2Ext4_no_data_limit_normal_dalvik.zip to the stock ROM about 4-months ago, not sure if that makes a difference or not.
When I search, it looks like the news is bad... most people that had this error gave up and believed it to be hardware NAND failure. Anything I can do to confirm or rule out NAND failure?
UPDATE: Managed to flash RUU, but results were interesting. It worked and it boots, home screen is blank (no HTC widgets), and apps I'd installed are still there. Clear Storage and Factory Reset does not get rid of them! I can manually uninstall apps, but when I reboot, they come back. I guess the /data must be stuck in some kind of read-only state.

GnatGoSplat said:
Using CWM 5.0.2.0, when I try to format /data, I get:
Error formatting /data!
When I try to format /cache, I get:
Error formatting /cache!
This all started because I decided to try Albinoman's AOSP 4.2 ROM. This is what happened:
1. Booted into CWM 5.0.2.0, made a nandroid backup of stock GB ROM.
2. Installed Albinoman's ROM using CWM, wiped /cache and /data.
3. Booted Albinoman's ROM, no problems. Decided I wanted to backup and restore some apps in the old ROM using Titanium Backup.
4. Restored nandroid backup of stock ROM. When it rebooted, all was well.
5. Used Titanium Backup to back up my apps.
6. Installed Albinoman's ROM again.
7. Cleared /data, it was fine. Cleared /cache. Stuck at "formatting" for half an hour.
8. Rebooted back to recovery and tried it again. Couldn't find E:.
9. Tried letting it boot. Stuck on the boot animation for 30-minutes.
10. Wipe everything and re-flash. Tried again. Still stuck on boot animation.
11. Manually unmount and tried to format /data and /cache, and I get the error messages.
I had installed Convert2Ext4_no_data_limit_normal_dalvik.zip to the stock ROM about 4-months ago, not sure if that makes a difference or not.
When I search, it looks like the news is bad... most people that had this error gave up and believed it to be hardware NAND failure. Anything I can do to confirm or rule out NAND failure?
UPDATE: Managed to flash RUU, but results were interesting. It worked and it boots, home screen is blank (no HTC widgets), and apps I'd installed are still there. Clear Storage and Factory Reset does not get rid of them! I can manually uninstall apps, but when I reboot, they come back. I guess the /data must be stuck in some kind of read-only state.
Click to expand...
Click to collapse
Did you reflash the Convert2Ext4 mod after you flashed the new rom? See this thread and read the top part after 'IMPORTANT:' There is a link in there to the old thread as well with a lot of info.

I did try that, but my /data and /cache are still unable to be written to, wiped, or formatted.
e2fsck won't touch /data, it has a superblock error. It finds errors on /cache and appears to be fixing them, but when I re-run it, the same errors are still there.

GnatGoSplat said:
I did try that, but my /data and /cache are still unable to be written to, wiped, or formatted.
e2fsck won't touch /data, it has a superblock error. It finds errors on /cache and appears to be fixing them, but when I re-run it, the same errors are still there.
Click to expand...
Click to collapse
Since you flashed the RUU, did you install an EXT4 compatible kernel or are you using the stock kernel? Maybe try restoring your working nandroid backup, then run the .zip to revert Convert2Ext4. Or even better, if you have a nandroid from before you installed the EXT4 mod.

DaggerDave said:
Since you flashed the RUU, did you install an EXT4 compatible kernel or are you using the stock kernel? Maybe try restoring your working nandroid backup, then run the .zip to revert Convert2Ext4. Or even better, if you have a nandroid from before you installed the EXT4 mod.
Click to expand...
Click to collapse
Wiping /data and /cache are enough to revert the mod.
Sent from my Galaxy Nexus using Tapatalk 2

Uggh, definitely doesn't sound so good. Since the RUU won't work, I'd say check out this thread:
http://forum.xda-developers.com/showthread.php?t=2123966

Yep, my partitions are no longer EXT4. #1 is EXT3 and #2 is EXT2. I guess that means Convert2Ext4 is no longer in play and the problem is unrelated.
Here is my parted:
Code:
parted /dev/block/mmcblk0 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 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext2
3 1007MB 7944MB 6937MB primary fat32 lba
Yeah, I read that thread and it didn't sound encouraging! I get pretty much the same errors.
Even rm 1 and rm 2 don't remove the partitions. It's like they're read-only. I'm using the parted from CWM 5.0.2.0. Should I use a different one?
Also when I try e2fsck on it:
Code:
~ # e2fsck -pf /dev/block/mmcblk0p1
e2fsck -pf /dev/block/mmcblk0p1
/dev/block/mmcblk0p1: recovering journal
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p1
~ # e2fsck -pf /dev/block/mmcblk0p2
e2fsck -pf /dev/block/mmcblk0p2
/dev/block/mmcblk0p2: Unconnected directory inode 34817 (/???)
/dev/block/mmcblk0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
~ # e2fsck -f /dev/block/mmcblk0p2
e2fsck -f /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Unconnected directory inode 34817 (/???)
Connect to /lost+found<y>? y
yes
Pass 4: Checking reference counts
Inode 2 ref count is 2, should be 3. Fix<y>? yes
Inode 34817 ref count is 3, should be 2. Fix<y>? y
yes
Pass 5: Checking group summary information
Block bitmap differences: +274 +(449--510) +(645--701) -(139524--139541) -(139
85--139800)
Fix<y>? yes
Free blocks count wrong for group #0 (7919, counted=7799).
Fix<y>? y
yes
Free blocks count wrong for group #17 (7934, counted=7929).
Fix<y>? yes
Free blocks count wrong (198324, counted=198199).
Fix<y>? y
yes
Free inodes count wrong for group #17 (2048, counted=2045).
Fix<y>? yes
Directories count wrong for group #17 (0, counted=1).
Fix<y>? y
yes
Free inodes count wrong (51189, counted=51186).
Fix<y>? yes
/dev/block/mmcblk0p2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p2: 14/51200 files (14.3% non-contiguous), 6601/204800 blocks
When I tried it without the -p is when it looks above like it's fixing something, but it really didn't fix anything because it does the same thing when I try e2fsck again (as if it's read-only).
Is MMCBLK0 one physical NAND chip? If so, how come I can read/write/erase the /emmc with no problems? Isn't that just another partition on the same NAND disk?
If /data and /cache are really bad, is there any possible way to do an equivalent of a low-level format on the NAND and repartition?

Is booting CWM 5.0.2.0 and using adb shell supposed to have root privileges?
I can't modify the partition table using either parted or fdisk. I even tried zeroing the partitions using dd if=/dev/zero of=/dev/block/mmcblk0p1, p2, and even the whole of mmcblk0, but nothing actually gets written.

Since it seems like the NAND is probably irreparably borked, can I approach this problem from a different angle?
Can I partition my sdcard with an ext3 and ext2 partition, and tell Android to use those as /data and /cache respectively?
What in Android maps /dev/block/mmcblk0p1 to /data and /dev/block/mmcblk0p2 to /cache, and can I change those to point to partitions on sdcard?
Or is that hard-coded into the kernel?

GnatGoSplat said:
Since it seems like the NAND is probably irreparably borked, can I approach this problem from a different angle?
Can I partition my sdcard with an ext3 and ext2 partition, and tell Android to use those as /data and /cache respectively?
What in Android maps /dev/block/mmcblk0p1 to /data and /dev/block/mmcblk0p2 to /cache, and can I change those to point to partitions on sdcard?
Or is that hard-coded into the kernel?
Click to expand...
Click to collapse
It is hard coded into the kernel. To get root in adbshell try typimg su. This seems to be happening to more and more people as these phones get up there in age.

GnatGoSplat said:
Since it seems like the NAND is probably irreparably borked, can I approach this problem from a different angle?
Can I partition my sdcard with an ext3 and ext2 partition, and tell Android to use those as /data and /cache respectively?
What in Android maps /dev/block/mmcblk0p1 to /data and /dev/block/mmcblk0p2 to /cache, and can I change those to point to partitions on sdcard?
Or is that hard-coded into the kernel?
Click to expand...
Click to collapse
The answer is yes to both actually. Thrle boot.img would need to be customized. The best way is a flashable zip in recovery. Data and cache would need to be wiped manually ad recovery will not pick this up. Expect poorer performance though as SD cards tend to be slower than built in storage.
Sent from my Galaxy Nexus using Tapatalk 2

Thanks! So it sounds like the way to make this work is to compile a custom kernel? I don't know the first thing about it, but I think I could learn.
This is only in the kernel, so I could flash any 3rd party D-Inc ROM and just flash my customized kernel and it will see /data and /cache on the sdcard?
I could probably get one of those fast Class 10 cards if it turns out this is too slow, but I do recall changing vold.fstab once to fool Android into seeing /emmc as /sdcard and the /emmc (as /sdcard) didn't benchmark all that much faster than a real sdcard. I'm assuming /data and /cache are the same speed as /emmc since they're on the same mmcblk0 device, so I'm thinking maybe sdcard performance would be acceptable.
This actually sounds like it could be a better long-term solution than replacing the motherboard because no telling if a new motherboard will fail soon too.

The motherboard should be reliable. Emmc may die. Especially considering how old current dincs are.
I was talking about the boot.img which is not ROM independent and kernels aren't always either. Best idea is a flashable zip to modify the ram disk but I need the partition names if you decide to do it. I recommend keeping cache and data in the same order.
Also there would need to be a flashable wipe script to wipe data and cache.
Sent from my Galaxy Nexus using Tapatalk 2

Sorry, I wasn't very clear. By motherboard failing, I was assuming NAND is soldered to the motherboard, and if that's the case, ruined NAND = ruined motherboard. I had thought maybe I could buy a DInc with smashed LCD and good motherboard and just swap into mine (because mine is MINT condition), but I thought if I do that, I could very well end up in the same place as I'm in now and using sdcard would be more of a guarantee I wouldn't have to worry about this again.
I think I understand, the boot.img and kernel aren't exactly the same thing, but the kernel is part of boot.img? Or is it only the RAMDisk that needs changed, or both? You mentioned partition names, are you offering to make these modifications for me?
By same order, do you mean because mmcblk0p1 is /data, mmcblk0p2 is /cache, and mmcblkp3 is /emmc, I should partition my sdcard the same way with data 1st, cache 2nd, and sdcard 3rd?
Should I partition it with the phone, PC, or does it matter? Should the sizes of the new /data and /cache be the same size as original, or is there any reason I should make them larger?
Could I wipe the new /data and /cache simply by booting into Recovery and using adb shell and format them?
Also, the commands I was issuing in adb shell were from booting into CWM Recovery. Is it possible that mode can't write because I didn't login as root using the su command? I hadn't thought that would be the problem seeing as how the RUU and Android itself can't write to /data and /cache and other people managed to fix partition problems without needing to run su.

GnatGoSplat said:
Sorry, I wasn't very clear. By motherboard failing, I was assuming NAND is soldered to the motherboard, and if that's the case, ruined NAND = ruined motherboard. I had thought maybe I could buy a DInc with smashed LCD and good motherboard and just swap into mine (because mine is MINT condition), but I thought if I do that, I could very well end up in the same place as I'm in now and using sdcard would be more of a guarantee I wouldn't have to worry about this again.
I think I understand, the boot.img and kernel aren't exactly the same thing, but the kernel is part of boot.img? Or is it only the RAMDisk that needs changed, or both? You mentioned partition names, are you offering to make these modifications for me?
By same order, do you mean because mmcblk0p1 is /data, mmcblk0p2 is /cache, and mmcblkp3 is /emmc, I should partition my sdcard the same way with data 1st, cache 2nd, and sdcard 3rd?
Should I partition it with the phone, PC, or does it matter? Should the sizes of the new /data and /cache be the same size as original, or is there any reason I should make them larger?
Could I wipe the new /data and /cache simply by booting into Recovery and using adb shell and format them?
Also, the commands I was issuing in adb shell were from booting into CWM Recovery. Is it possible that mode can't write because I didn't login as root using the su command? I hadn't thought that would be the problem seeing as how the RUU and Android itself can't write to /data and /cache and other people managed to fix partition problems without needing to run su.
Click to expand...
Click to collapse
The NAND is likely soldered to the motherboard, so you're right about that.
To answer your first question, yeah, the kernel is part of the boot.img. The other part is the RAMdisk which is the only thing that needs to be changed.
Partition it in the same order. Probably parted via adb shell. 100MB for cache and at least 750MB for data. Sizes don't matter too much but you want enough.
adb shell has root access automatically in recovery. The issue is hardware most likely so your proposed workaround may be the only option.
First plan of attack is to find the partition names which would be mmcblk1p1 and mmcblk1p1 if you partition the sdcard the same way as the ROM is partitioned. Ideally you need to be able to fix the partitions themselves. I'll try to give more info later.

I copied the partition sizes from mmcblk0, so here's what I have on my 16GB SD card:
Code:
Model: SD SA16G (sd/mmc)
Disk /dev/block/mmcblk1: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext2
2 797MB 1007MB 210MB primary ext2
3 1007MB 16.0GB 15.0GB primary fat32 lba
mmcblk1p1 for /data
mmcblk1p2 for /cache
mmcblk1p3 for /sdcard
Will that work? I couldn't get mmcblk1p1 to show up as ext3. I did use mke2fs -j /dev/block/mmcblk1p1 to format it and I've read ext3 = ext2+journal, so I guess the fact it's not saying "ext3" under filesystem is okay?

GnatGoSplat said:
I copied the partition sizes from mmcblk0, so here's what I have on my 16GB SD card:
Code:
Model: SD SA16G (sd/mmc)
Disk /dev/block/mmcblk1: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext2
2 797MB 1007MB 210MB primary ext2
3 1007MB 16.0GB 15.0GB primary fat32 lba
mmcblk1p1 for /data
mmcblk1p2 for /cache
mmcblk1p3 for /sdcard
Will that work? I couldn't get mmcblk1p1 to show up as ext3. I did use mke2fs -j /dev/block/mmcblk1p1 to format it and I've read ext3 = ext2+journal, so I guess the fact it's not saying "ext3" under filesystem is okay?
Click to expand...
Click to collapse
You would be correct. Yes, that's fine.

Thanks, what should be my next steps?

GnatGoSplat said:
Thanks, what should be my next steps?
Click to expand...
Click to collapse
I'll have to find time to make scripts that will modify the ramdisk, unless you can just extract it and make the changes yourself.

That would be great, I really appreciate all the help so far.
Do you think ramdisk is the only place a change will need to be made?
I was trying to see if I could figure out how to extract ramdisk from boot.img and found a perl script, but I haven't gotten around to playing with it.

[Q] Can't Boot but can get into recovery, fastboot, and ADB but nothing seems to work

If I try to boot normally I get stuck on the boot screen. I can go into recovery (Clockwork Mod) but no combination of Flashing partitions seems to do anything. The one thing I've noticed is in Mounts and Storage /system; /data; /firmware/mdm; and /firmware/q6 all can be mounted. I can mount both /system and /data but the 2 /firmware partitions wont mount and if I check the log it reads
mount: mounting /dev/block/mmcblk0p16 on /firmware/q6 failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p16 (No such file or directory)
Error mounting /firmware/q6
I don't know if these 2 partitions would prevent booting up if they fail to load or if its something totally different. I've tried flashing just about everything I can find and nothing seems to take. Any help would be fantastic, if you need more info, just ask and I will do my best to get it for you. Thank You

fischerdave said:
If I try to boot normally I get stuck on the boot screen. I can go into recovery (Clockwork Mod) but no combination of Flashing partitions seems to do anything. The one thing I've noticed is in Mounts and Storage /system; /data; /firmware/mdm; and /firmware/q6 all can be mounted. I can mount both /system and /data but the 2 /firmware partitions wont mount and if I check the log it reads
mount: mounting /dev/block/mmcblk0p16 on /firmware/q6 failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p16 (No such file or directory)
Error mounting /firmware/q6
I don't know if these 2 partitions would prevent booting up if they fail to load or if its something totally different. I've tried flashing just about everything I can find and nothing seems to take. Any help would be fantastic, if you need more info, just ask and I will do my best to get it for you. Thank You
Click to expand...
Click to collapse
I was in a similar situation a few months back. Have you tried flashing a RUU? Preferably the current version or a newer version.
http://forum.xda-developers.com/showthread.php?p=46506621

Can remember if I did or not so probably worth a shot
I'm Downloading now and will let you know how that goes. Thanks.

fischerdave said:
I'm Downloading now and will let you know how that goes. Thanks.
Click to expand...
Click to collapse
Give me a holler of you don't get it booted.

How to Build new recovery modded for Zopo zp999 or 3X mtk 6595M

How to Build new recovery modded for Zopo zp999 or 3X Mtk 6595M ​
In this thread we will discuss how to create or build new recovery modded for Zopo zp999 Mtk 6595M.
Everybody are Welcome!​
MANY THANKS TO OUR MODERATOR TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​

Software section​
Firmware
http://www.needrom.com/download/zopo-3x/

Procedure Section
In this new Phone there are new memory sectors!​

Thread under construction​

Hello everyone, alllora 999 has one partition , I tried to compile several times TWRP but with the classic method for mtk does not work. Even the cwm works , you accept advice

I'm following the thread, interested to understand the new recovery for mediatek 6595 cpus

marsapa said:
Hello everyone, alllora 999 has one partition , I tried to compile several times TWRP but with the classic method for mtk does not work. Even the cwm works , you accept advice
Click to expand...
Click to collapse
MTKtools doesn't seem to work at the moment, either.

csdhhong said:
MTKtools doesn't seem to work at the moment, either.
Click to expand...
Click to collapse
Yes this is true.
Mtkdroid tools maybe not compatible with the mtk 6595
Sent from my GT-I9505 using XDA Free mobile app

ghost45 said:
Yes this is true.
Mtkdroid tools maybe not compatible with the mtk 6595
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Hi @ghost45,
I know very little about this phone and I do not have one. so I can only offer some observations.
Questions.
1. Has anyone got their hands on an update.zip yet?
2. Does spflashtool still work with this phone?
Thought:
If there is only 1 partition then maybe the ROM is in fact more like a .ISO or live DVD
Has anyone tried to Mount the partition in such a way?
Just thinking out loud guys.

bigrammy said:
Hi @ghost45,
I know very little about this phone and I do not have one. so I can only offer some observations.
Questions.
1. Has anyone got their hands on an update.zip yet?
2. Does spflashtool still work with this phone?
Thought:
If there is only 1 partition then maybe the ROM is in fact more like a .ISO or live DVD
Has anyone tried to Mount the partition in such a way?
Just thinking out loud guys.
Click to expand...
Click to collapse
Hi Big,
Yes flashtool have problems... Run only the last version n. 5.xxxx
There is only one partition.. So i think, probably, this big primary partition is not good for the recovery mod that try to find the sd memory and sd internal memory..
I must study too much.
Thanks for your help... You know are always welcome.... Elsewhere!
Understood?
Sent from my GT-I9505 using XDA Free mobile app

Can someone please explaie how to root this model? I don't want to flash a custom ROM, just to root it.

hopeayaska said:
Can someone please explaie how to root this model? I don't want to flash a custom ROM, just to root it.
Click to expand...
Click to collapse
Custom rom?
Where is it?
There isn't any recovery modded for this phone.
Sent from my GT-I9505 using XDA Free mobile app

I don't think there are any custom ROMs yet, but since the space in the device has only one partition and without root you can't transfer the apps in the SD card. DO you think Vroot will work with it?

hopeayaska said:
I don't think there are any custom ROMs yet, but since the space in the device has only one partition and without root you can't transfer the apps in the SD card. DO you think Vroot will work with it?
Click to expand...
Click to collapse
According me there isn't reason to transfer the app in the sd card... The space is too big and there isn't internal memory like internal sd like before.
In this phone there is only one partition system =data.
Vroot and all the type of root aren't able to receive right root.
We wait for the great Russian Seven Max that could create new recovery mod for this mtk 6595.
After this step we will try to start to all the root procedure under recovery to mod this phone.
Sent from my GT-I9505 using XDA Free mobile app

ghost45 said:
According me there isn't reason to transfer the app in the sd card... The space is too big and there isn't internal memory like internal sd like before.
In this phone there is only one partition system =data.
Vroot and all the type of root aren't able to receive right root.
We wait for the great Russian Seven Max that could create new recovery mod for this mtk 6595.
After this step we will try to start to all the root procedure under recovery to mod this phone.
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
According to the fstab in the official recovery you definitely have partitions
Code:
boot /boot emmc defaults defaults
/dev/block/mmcblk0p2 /cache ext4 defaults defaults
/dev/block/mmcblk0p3 /data ext4 defaults defaults
misc /misc emmc defaults defaults
recovery /recovery emmc defaults defaults
/dev/block/mmcblk0p4 /sdcard vfat defaults defaults
/dev/block/mmcblk0p6 /system ext4 defaults defaults
# Vanzo:songlixin on: Wed, 22 Feb 2012 18:31:03 +0800
# To support external sdcard
/dev/block/mmcblk1p1 /sdcard2 vfat defaults defaults
# End of Vanzo:songlixin
Of course I suppose these could be fake but I do not know why they would put in a fake recovery.
Please try these
You flash At your own risk of course as I do not have a phone to test it on. :crying:
Mods are made to the needrom .img's that you posted in the first post so do not flash if in any doubt that this rom is incorrect.
CWM Recovery modded by me so now should hopefully support sdcard internal (emmc) external sdcard (vfat) sd-ext (auto) and maybe even usb-otg (auto) :fingers-crossed:
(init.rc edited and recovery.fstab)
Code:
/boot dev/bootimg emmc defaults defaults
/misc dev/misc emmc defaults defaults
/recovery dev/recovery emmc defaults defaults
/logo dev/logo emmc defaults defaults
/misc dev/misc emmc defaults defaults
/nvram dev/nvram emmc defaults defaults
/uboot dev/uboot emmc defaults defaults
/dev/block/mmcblk0p2 /cache ext4 defaults defaults
/dev/block/mmcblk0p3 /data ext4 defaults defaults
/dev/block/mmcblk0p6 /system ext4 defaults defaults
/dev/block/mmcblk0p4 /sdcard vfat defaults defaults
/dev/block/mmcblk1p1 /sdcard2 vfat defaults defaults
/dev/block/mmcblk1p2 /sd-ext auto defaults defaults
/dev/block/sda1 /usb-otg auto defaults defaults
It will be almost impossible to make TWRP fit in the recovery partition of this phone as it is just too small. Maybe later you can workout how to resize the partitions.
I modded the shoe image too so now unsecured with adb
Code:
boot=shoe
for rename hope you understand.
Warning!! Only flash this if the recovery works fine and you have made a successful backups.

Hi big,
your recovery mod not boot remaining in black boot like the recovery of Seven.
I see the block in the files but i do not understand if them are fake or i can't able to see these new sectors.
i see only one partition system=data
I try also:
rename the file shoe in:
boot.img
and the recovery that you have made
but not run at all the phone remaining in boot!
see you and thanks for your great help.

ghost45 said:
Hi big,
your recovery mod not boot remaining in black boot like the recovery of Seven.
I see the block in the files but i do not understand if them are fake or i can't able to see these new sectors.
i see only one partition system=data
I try also:
rename the file shoe in:
boot.img
and the recovery that you have made
but not run at all the phone remaining in boot!
see you and thanks for your great help.
Click to expand...
Click to collapse
Ok bro Sorry it did not work it's difficult to help without actually having the phone in my hands.
If what you say is true then I would ask someone with linux to try mount the single partition as you would mount an .iso
I read some place that Total Commander for pc maybe able to mount the entire drive without the need of root. :fingers-crossed:
Regards bigrammy.

bigrammy said:
Ok bro Sorry it did not work it's difficult to help without actually having the phone in my hands.
If what you say is true then I would ask someone with linux to try mount the single partition as you would mount an .iso
I read some place that Total Commander for pc maybe able to mount the entire drive without the need of root. :fingers-crossed:
Regards bigrammy.
Click to expand...
Click to collapse
Thanks big... Yesterday i work to hard together other friends that we known.. But nothings..
Sent from my GT-I9505 using XDA Free mobile app

ghost45 said:
Thanks big... Yesterday i work to hard together other friends that we known.. But nothings..
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Ok I have done some more research and changed the recovery fastab's to this.
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/vendor /vendor ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/misc /misc emmc defaults defaults
/devices/platform/mtk-msdc.0/mmc_host auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/platform/mtk-msdc.1/mmc_host auto vfat defaults voldmanaged=sdcard1:auto
/devices/platform/xhci-hcd auto vfat defaults voldmanaged=usbotg:auto
You can now retry and see if this will now work it may require a little more editing but lets see what works and what does not first. :fingers-crossed:

bigrammy said:
Ok I have done some more research and changed the recovery fastab's to this.
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/vendor /vendor ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/misc /misc emmc defaults defaults
/devices/platform/mtk-msdc.0/mmc_host auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/platform/mtk-msdc.1/mmc_host auto vfat defaults voldmanaged=sdcard1:auto
/devices/platform/xhci-hcd auto vfat defaults voldmanaged=usbotg:auto
You can now retry and see if this will now work it may require a little more editing but lets see what works and what does not first. :fingers-crossed:
Click to expand...
Click to collapse
Thanks... I will try it.
But according me the problem is connected with the repack operation... Or as someone sayed pack operation.
Sent from my GT-I9505 using XDA Free mobile app

[GUIDE] How to flash a ROM on an encrypted device with TWRP.

THIS WILL WIPE YOUR DATA
Android's encryption of the /data partition cannot be unlocked via TWRP or other recoveries. The normal "wipe data/factory reset" will fail, because /data can't be accessed.
I assume your phone has root, and you know how to get a root shell in ADB. There are tons of guides for that, but very few (none that I could find) for this.
First, in your root shell, run:
Code:
cat /etc/fstab
and copy the output to a text file or such where you can refer back to it. You should get something like this:
Code:
/dev/block/mmcblk0p16 /system ext4 rw
/dev/block/mmcblk0p29 /data ext4 rw
/dev/block/mmcblk0p18 /cache ext4 rw
/dev/block/mmcblk0p10 /efs ext4 rw
/external_sd vfat rw
/usb-otg vfat rw
/dev/block/mmcblk0p1 /modem vfat rw
But the /dev/block/... bits may be different for different devices. Mine is a T-Mobile Samsung Galaxy S 4.
Find the line with /data listed on it. In my case, that's "/dev/block/mmcblk0p29 /data ext4 rw".
Then you'll need just the first part. In my case, that's "/dev/block/mmcblk0p29". Using mke2fs we'll format the appropriate block device as ext4.
Code:
mke2fs -t ext4 /dev/block/mmcblk0p29
If your block device is different, then USE YOURS. Using the wrong block device will format the wrong partition. Formatting the /efs partition has been known to brick phones.
This will take a few minutes to complete. Once done, you will have a blank unencrypted /data partition.
Then you can do a normal data wipe/factory reset, install the rom, etc.

Thanks for sharing this but surely it's a lot easier/safer just to Format Data from TWRP?

doveman said:
Thanks for sharing this but surely it's a lot easier/safer just to Format Data from TWRP?
Click to expand...
Click to collapse
Read paragraph after the all caps

serio22 said:
Read paragraph after the all caps
Click to expand...
Click to collapse
Yes, the normal wipe/factory reset doesn't work when it's encrypted but format does. I just did it myself from TWRP for the very reason that there was no other way to factory reset and it worked fine.

Keyword "format" vs "wipe" , it's like the obelisk from "2001", you don't mess with "format" .
Pp.

PanchoPlanet said:
Keyword "format" vs "wipe" , it's like the obelisk from "2001", you don't mess with "format" .
Pp.
Click to expand...
Click to collapse
Er, from the OP
"Then you'll need just the first part. In my case, that's "/dev/block/mmcblk0p29". Using mke2fs we'll format the appropriate block device as ext4.
mke2fs -t ext4 /dev/block/mmcblk0p29"
So that's just formatting it, with the additional risk of failying to identify the correct dev and formatting something you shouldn't!