Anyone know whats causing the following issue?
Recently when I download the latest Nightly's (to flash over current Nightly) and boot into recovery and try to flash the ROM, I get the following:
Code:
Installing Update......
E: Error in /sdcard/cm_vision_full-119.zip
(Status 1)
Installation aborted
Before I proceed with trying to flash the ROM I do clear cache and dalvik cache, I always do this. But lately Ive been getting that error when ever I download the file from the phone's browser (whether it be stock, Miren, etc) or even from computer and transfer it to SD card and try to flash. Sometimes when I download from my computer browser and transer to SD card it works the second time (or if I transfer the first file over again) but when I reboot into the ROM, apps are missing and etc. So it corrupted the install.
Things Ive tried with no success
1. Reformatting SD Card
2. Complete Data Wipe (which allows me to flash the Nightly with nothing previously installed) but when I try to flash a new nightly over the installed one same issue
3. Reinstalling Recovery
4. Downloading rom from either WiFi or Tmobile network
5. Going back to G2 Engineering Hboot
Im at the point where I frustrated with my G2 and want to throw it against a wall. The only way Im able to flash new Nightly's is through wiping the device, which gets tedious.
Bump someone has to have some solution.
is signature verification enabled in CWM? when you go to install zip from sdcard, make sure you toggle signature verification to OFF. not sure if this is what you're encountering, it almost sounds like a bad sd card too.
pmcqueen said:
is signature verification enabled in CWM? when you go to install zip from sdcard, make sure you toggle signature verification to OFF. not sure if this is what you're encountering, it almost sounds like a bad sd card too.
Click to expand...
Click to collapse
Signature verification is always off. I did try to turn it on to see if it made a difference, didn't. Ive pretty much tried everything I could think of.
I did have one issue with the SD card (dont know if it is related or not), when I was trying to copy a file to my SD under Ubuntu, it wouldnt let me saying the SD Card is read-only. I went into Windows and it let me transfer the files, so I dont know.
sounds like it could be SDcard related because its happening whether you download via the phone or computer. Have you tried wiping and formatting the SDcard and trying agian?
boost3d23 said:
Signature verification is always off. I did try to turn it on to see if it made a difference, didn't. Ive pretty much tried everything I could think of.
I did have one issue with the SD card (dont know if it is related or not), when I was trying to copy a file to my SD under Ubuntu, it wouldnt let me saying the SD Card is read-only. I went into Windows and it let me transfer the files, so I dont know.
Click to expand...
Click to collapse
do you have another sd card lying around that you can test with? a malfunctioning sdcard can manifest itself in some pretty wonky ways, including something like what you're describing. that would be my next move in troubleshooting.
seems especially likely since you've already tried downloading the rom different ways and whatnot.
do you have eng hboot? you could try fastboot flashing CWM again just to make sure nothing is going wrong there. I would do it manually via PC10IMG or fastboot flash rather than rom manager... I don't really trust the app to do any of its recovery functions "properly" anymore.
martonikaj said:
sounds like it could be SDcard related because its happening whether you download via the phone or computer. Have you tried wiping and formatting the SDcard and trying agian?
Click to expand...
Click to collapse
Tried wiping and reformatting the card many of times. Most of it through Clockworkmod recovery not through the PC though.
pmcqueen said:
do you have another sd card lying around that you can test with? a malfunctioning sdcard can manifest itself in some pretty wonky ways, including something like what you're describing. that would be my next move in troubleshooting.
seems especially likely since you've already tried downloading the rom different ways and whatnot.
do you have eng hboot? you could try fastboot flashing CWM again just to make sure nothing is going wrong there. I would do it manually via PC10IMG or fastboot flash rather than rom manager... I don't really trust the app to do any of its recovery functions "properly" anymore.
Click to expand...
Click to collapse
I do have another SD card that I could test with, haven't done that yet though. Will try it, wasnt sure if it was SD card related.
Yes I do have eng hboot; I flashed the G2 one then the Desire Z one (using the Virtous rom guide) and finally back to the G2 one. Thought that might of been the reason for the issues but turned out to not be.
And I agree I only use ROM Manager to do backups. Anyway I flashed the Clockworkmod 3.1.0.1 (by blahbl4hblah) through recovery and then went back to the one in rom manager. Havent tried installing it through fastboot. Will try that as well.
Ok I can say its not the SD Card or recovery. I flashed recovery again through fastboot and used a different SD Card. Still throws that error. I made sure to only copy my media to the SD Card and nothing from the previous one to make sure it wasnt some file on there that was causing the issue.
Edit: And here is the worst part. After the install fails and I reboot Im stuck at the HTC logo, so Im forced to wipe and reinstall.
Bump for a possible solution.
Another note. The same file I downloaded (didn't redownload) that throws that error when I try to flash it over a old Nightly, works when I wipe data/factory reset.
Ex. I downloaded Nightly 140 and try to flash it over Nightly 139, it throws that error. Now I wipe data/factory reset and flash that same Nightly 140 (didnt redownload) and flash it, it works.
What the heck is going on. I unrooted and re-rooted my G2 and still have this issue.
Bump still having this issue.
This is the CWM Recovery Error Log
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p25 (Invalid argument)
-- Wiping cache...
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
52624 inodes, 209715 blocks
10485 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=262144
26 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Creating journal inode: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/52624 files (0.0% non-contiguous), 10771/209715 blocks
Cache wipe complete.
E:unknown volume for path [/sd-ext]
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
-- Installing: /sdcard/cm_vision_full-145.zip
Finding update package...
I:Update location: /sdcard/cm_vision_full-145.zip
Opening update package...
Installing update...
about to run program [/tmp/backuptool.sh] with 2 args
Creating filesystem with parameters:
Size: 435943936
Block size: 4096
Blocks per group: 32768
Inodes per group: 6652
Inode size: 256
Journal blocks: 1663
Label:
Blocks: 106431
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/26608 inodes and 3437/106431 blocks
error: file_write: write: I/O error
E:Error in /sdcard/cm_vision_full-145.zip
(Status 1)
Installation aborted.
Have you checked md5 sum of downloads?
Sounds like either card corruption or filesystem corruption.
Tried doing any kind of chkdisk or equivalent on the card?
Sent from my HTC Vision using XDA Premium App
Mnementh666 said:
Have you checked md5 sum of downloads?
Sounds like either card corruption or filesystem corruption.
Tried doing any kind of chkdisk or equivalent on the card?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Yeah the MD5 sum of the downloads are okay.
Havent run a chkdisk of the SD card. Will do that. Ive reformatted the SD card and tried a different SD card and still have the same issue.
How do I know if it is a filesystem corruption and anyway to fix that?
Hmmm. Have you had any issues with connecting the phone and using as a usb drive? Maybe try copying a large (>250mb) file to the SD from your computer, and then copying back from phone to pc.
The read-only error you mentioned earlier is I think going to be the root cause, somehow. I'm not familiar offhand how the microSD can set RO or RW, but on the normal SD it's a switch.
Maybe something in the microSD card slot is causing errors?
Sent from my HTC Vision using XDA Premium App
Mnementh666 said:
Hmmm. Have you had any issues with connecting the phone and using as a usb drive? Maybe try copying a large (>250mb) file to the SD from your computer, and then copying back from phone to pc.
The read-only error you mentioned earlier is I think going to be the root cause, somehow. I'm not familiar offhand how the microSD can set RO or RW, but on the normal SD it's a switch.
Maybe something in the microSD card slot is causing errors?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Ran a chkdsk on the SD Card and no issues were found.
No problems connecting the phone to PC and using the usb drive. I tested transfering a 367MB file back and forth and it worked perfectly.
The interesting thing is Im not able to flash the Nightly ()without completely wiping) but Im able to use the same flashing method and flash a kernel perfectly without getting this error.
No clue what in the SD Card slot could cause the issue. The card is seated properly and locked into place.
Well... unfortunately, that taps out all my knowledge. Wish I could help more.
My thought on the card slot was just something (dust? Debris?) that got in there and is causing random intermittent r/w errors on the card. Basically like corrupting the file.
Do you download the nightly file through rom manager? Load the zip through same?
If yes... maybe download on pc, transfer to card, boot recovery, install directly.
You've probably tried that, and if so I apologize. I'm @ work and can't read the site, and replying and reading simultaneously isn't possible on tapatalk and I'm grasping at straws :-D
Sent from my HTC Vision using XDA Premium App
Mnementh666 said:
Well... unfortunately, that taps out all my knowledge. Wish I could help more.
My thought on the card slot was just something (dust? Debris?) that got in there and is causing random intermittent r/w errors on the card. Basically like corrupting the file.
Do you download the nightly file through rom manager? Load the zip through same?
If yes... maybe download on pc, transfer to card, boot recovery, install directly.
You've probably tried that, and if so I apologize. I'm @ work and can't read the site, and replying and reading simultaneously isn't possible on tapatalk and I'm grasping at straws :-D
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Nope there was no issue with SD card slot that I could see with the naked eye.
Honestly dont use ROM Manager at all. I either download from the phones browser (stock or Miren) or through my PC and transfer it to the SD; both resulting in the issue.
Here's what I think it is, I think its a issue with the phone's partition/filesystem. The result of switching to the Desire Z Eng Hboot. But Ive went back to the G2 Eng Hboot and stock Hboot, many times. So Im not sure.
Anyway thanks for attempting to help. You gave me some additional stuff to look into.
Related
First off thanks for all the wonderfull help. I finally managed to flash jf1.51 and get the phone running again. Kinda hard 2 do without a sdcard and when fastboot didnt work!!!!!
Now that the phone is running again I STILL have no sdcard slot!! The phone just says...
Removed SD card
The SD has been removed. Insert a new SD card to increase your device
No one has had this problem....
********Original********
We will start with what happened up till that point.
I originally was using haykuro hero with apps2sd (Original Tmobile 1gb sdcard) It worked but slow and crashing on just about everything.
Did the multiple speedups / optimizations for hero.
Switched too Superheros beta v1 hero rom. (No problems other than slow/app crashing)
Ordered a new Transcend 4gb class 6 sdcard.
Waited until I received the new card before switching too Superheros beta v2.
Setup the partitions on the new 4gb just like I had done with the 1gb (and the 1gb had no problems except 4 being slow)
Updated to superheros beta v2 rom. Everything went fine, had like 9mb free (I used the full Rom) After the phone was setup and rom was booted. Used the app2sd app built into the rom. Moved the apps/cache 2 sdcard. Rebooted phone and had a bootloop (kept replaying the htc boot animation)
So remembering reading when hero first came out. I assumed that some of the files for hero did not transfer too the sdcard (Remember when people had problems with app_s.zip)
So I go into the bootloader mode (home + power) to reflash the rom and receive this error (Now during this time I still have the 4gb in)
Installing from sdcard...
Finding update package...
E:Can't mount /dev/black/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
--------------------------------
I have tried 4 different sdcards with 3 different sdcard readers and every one of them has this error. I have tried wiping but didnt change anything.
It is like the phone cannot see any sdcard anymore. I can adb but I dont know anything that could help.
Thanks
-Matt
**Edit**
Have tried partitioning to only fat16 and fat32 on sdcards.
Have tried fastboot with dreaimg.nbh and still does not detect sdcard.
Have tried putting app_s.zip into ext2 partition.
Have tried Downloading different roms and rom types.
Have tried "mount /sdcard" *error mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory*
Have tried Pushing app and app_s to /data from update.zip
Have tried copying app and app_s to /mmcblk0p2 from a linux os "Phone will not detect either partitions" (/mmcblk0p1 is fat32. /mmcblk0p2 is ext2)
Have tried editing mountd.conf and init.rc
Everytime I try and apply update.zip I get these weird files on the sdcard. (http://www.pcxpressrepair.com/android/qxdm_20080904_032341_1.dm , http://www.pcxpressrepair.com/android/qxdm_20080904_032607_1.dm There are just 2 that I uploaded.
Also here is a Logcat of when the phone is trying to boot (bootloop)
http://www.pcxpressrepair.com/android/logcat1.txt
During bootloop here are the mounts
--------------------------------------------
Filesystem Size Used Available Use% Mounted on
tmpfs 48.2M 0 48.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 90.0M 76.7M 13.3M 85% /system
/dev/block/mtdblock5 89.8M 14.7M 75.1M 16% /data
/dev/block/mtdblock4 30.0M 1.1M 28.9M 4% /cache
I have had similar problems but it was because of a bad download. Or I disconnected the phone to quickly from the USB before selecting remove.
Wrong forum. Mods, lock this thread pronto!
Also I received a letter from tmobile saying that they are going to drop me because of roaming too much. I would be nice to get this worthless phone running again. I have until July 7th 2 switch carriers. Because my G1 is basically a paperweight now I was thinking of getting the HTC lancaster with AT&T but it will not be on the market in time.
By the way the phone is acting and no one else having this problem. I am lead 2 believe that this is a hardware issue with the G1. But, every time I try and flash the rom I get that weird file on my fat32 partition. So I would assume that the phone can still write to the sdcard, even though it cannot mount it. So don’t know if it is hardware or not. But, tonight I will disassemble the phone. (Because I’m not getting 2 much help here)
Also if apps2sd or cache failed when the rom was running for a moment what would be a way to restore it back (If the phone worked and no apps2sd is still fine 4 me!). Every time I try and link back 2 the phone it cannot find the directories that are on the sdcard (obvious cuz the sdcard is not mounted) I had this problem before but, the sdcard was mountable so there was no problem.
Would there be a configuration file that I can pull, modify, and then push back with the app2sd/cache info on it. I am moments away from pushing the entire update.zip 2 the phone. I am running out of options on what 2 do or how 2 fix.
-Matt
phone wont even turn on now.
Will it blend? Post results.
As soon as I get a blender
Same Prob
I'm having the exact same problem, has anyone found a solution yet?
Same issue here! Reformatted, wiped the works and nothing. And I have searched everywhere and like you it seems hardly anyone has this same issue. If I can't get it resolved soon I am getting the phone replaced.
I have got the same problem on my vodafone HTC Magic. Can boot to spl, fastboot to recovery rom but cannot mount SD Cards. Anyone found a solution?
Damnit.. My company required encryption of the data on my Nexus S when I was testing ICS Beta with Email / Exchange.
Went ahead and encrypted the device.
Then, I wanted to install ICS Combo Beta 11, so I formatted /system /data /boot and tried to install from /sdcard/*.zip.
No luck.
Clockworkmod recovery cannot mount /sdcard anymore.
Wanted to try and format it, but the clockworkmod tries to mount it first, before formatting
HELP!
I'm stuck with only recovery now and no way to get the update package installed
Is there a way to install from zip via the command line?
You should be able to use fastboot to load the rom on your device. I haven't tried it this way before but it should work:
Code:
fastboot update rom.zip [-w if you want to erase data too]
Give it a spin.
The SDCard not being able to be mounted has been covered a few times but I can't recall the proper fix by heart - search around and you'll definitely get some results that can help you with that.
Greetz
Sounds like it's busted.
Sent from my Nexus S using xda premium
Can you still enable USB Mass Storage in recovery? Try reformat the SD from your desktop?
Si_NZ said:
Can you still enable USB Mass Storage in recovery? Try reformat the SD from your desktop?
Click to expand...
Click to collapse
Thought about that, but what filesystem? FAT32?
Sure
Greetz
I had the same problem with one of the first ICS betas.
Formatting to FAT32 on my Mac was not enough, I had also to reformat under Android. Hope, you backed up your data
dr911 said:
I had the same problem with one of the first ICS betas.
Formatting to FAT32 on my Mac was not enough, I had also to reformat under Android. Hope, you backed up your data
Click to expand...
Click to collapse
Definately backed up..
This was a real scare.. I couldn't mount or format from clockworkmodrecovery. All I had was the adb shell and the builtin /sbin commands.
LUCKILY I found this article;
http://forum.cyanogenmod.com/topic/...mmcblk0++mkfs++ext2__fromsearch__1#entry56396
It didn't exactly match what I was experiencing, but the key was the parted program.
Using it, I was able to reformat my media (partition 3) and am now able to repush things to it.
Stupid sdcard encryption..
Reinstalling ICS Beta 11 now
Blood pressure slowly decreasing.. damn that was a nightmare
So some lessons learned;
DON'T try to partition your SDCARD from clockworkmod or Windows or Mac. The USB storage presented to your computer is a single partiton from you mmcblk0 sd storage. If you partition it, you've got a partition inside a partition which will only make sense to your windows/mac system. Inside of Android, the partition is essentially corrupted and it won't mount.
Formatting from Windows only makes it appear to be working.. in reality you've created a second partition and it's corrupted from the Android point of view.
parted is the only way to fix it. from parted do mkfs type fat32 partiton 3 (media) that will reformat the partition correctly and give you access from Android and external USB hosts.
That's weird...
People have been able to format the SD as ext4 on a desktop using Ubuntu for example. I don't understand how that is different to mkfs.ext4 vs mkfs.vfat. I mean why am I confined to formatting on the phone itself? I'm really confused now.
On a side note. What you experienced is totally expected if you think about it carefully. It's like you have just lost the key to open your SD content by wiping the phone, of course it can no longer be mounted. But I'm not sure why it cannot be simply formatted in CWM.
nauckwj said:
Formatting from Windows only makes it appear to be working.. in reality you've created a second partition and it's corrupted from the Android point of view.
Click to expand...
Click to collapse
That means, I should check my SD Card, which I formatted under OSX with Disk Utility?
Maybe I'll do it next time I flash a new ROM, because for now it works fine.
nauckwj said:
Blood pressure slowly decreasing.. damn that was a nightmare
Click to expand...
Click to collapse
Yeah, I had a similar situation a few weeks after I got my beloved NS when I tried Whispercore. The hole NS got encrypted and formatting the system partition in CWM didn't work, but what I read it was luckily due to a problem with the CWM version. Flashing a newer Version of CWM solved the problem. First I was dying!
So, when I encrypted with ICS and got this problem I calmed down much faster
Si_NZ said:
That's weird...
People have been able to format the SD as ext4 on a desktop using Ubuntu for example. I don't understand how that is different to mkfs.ext4 vs mkfs.vfat. I mean why am I confined to formatting on the phone itself? I'm really confused now.
On a side note. What you experienced is totally expected if you think about it carefully. It's like you have just lost the key to open your SD content by wiping the phone, of course it can no longer be mounted. But I'm not sure why it cannot be simply formatted in CWM.
Click to expand...
Click to collapse
My problem was I used the Windows fdisk partitioning utility to repartition my /sdcard partition. That was part of the problem. I did also read how some people were repartitioning the /sdcard partition, which is kind of weird. I can understand why someone might want to reformat it as an ext4 filesystem, but why would you want to partition a partition?
The /sdcard partition is actually the third partition on your mmcblk0 device. If you partition it, most utilities will fail to recognize it as a valid media device anymore, because they expect to be able to read the filesystem data structures when they mount it. These won't exist if a partition table is sitting at the beginning of the blocks.
I couldn't reformat from within CWM because it first tries to mount the partition. if it fails to mount, CWM won't reformat it. Only way to reformat it was with parted, unless you have a working system installation.
Last night I was also able to reformat it from within ICS. Had to do a full factory-wipe from within ICS, then it indicated the sdcard was no longer valid and asked me if I wanted to reformat it. Once I said yes, all was back to normal.
Fun fun
I bypassed dead internal memory on a GT-I9000M.
Symptoms:
- Your GT-I9000M is not booting or bootlooping no matter what firmware you are flashing it with.
- In recovery, you are seeing I/O errors on /dev/block/mmcblk0p1
- Trying to repartition and format the internal storage with fdisk or parted and mkfs.whatever fails.
To recover:
- Partition and format your 16GB+ external microSD with at least two primary partitions, vfat on the first one and rfs (or whatever fs is supported by your firmware) on the second one.
- Acquire a stock ROM, in my case I used JL2
- untar the PDA portion of your ROM of choice (you want zImage and factoryfs.rfs)
- Extract initramfs from zImage ( https://github.com/mistadman/Extract-Kernel-Initramfs )
- grep for /dev/block/mmcblk, there should be 4 .rc files containing references to it as well as within the binary file /init.
- use a text editor to replace all occurances of "mmcblk0" with "mmcblk1" (and vice-versa if you feel so inclined) in the .rc files.
- use a hex editor to replace "mmcblk0" with "mmcblk1" in /init.
- create cpio archive of your modified initramfs with `find . | cpio -H newc -o > ../initramfs.img`
- repack kernel and initramfs ( http://forum.xda-developers.com/showthread.php?t=789712 ), you should have a new_zImage now.
- Mount the factoryfs.rfs as a loop `mount -o loop,rw -t vfat factoryfs.rfs /mnt/loop`
- Modify vold.fstab - this topic is well covered elsewhere (swap sdcard and sdcard1, swap mount points), then umount your loop
- Flash factoryfs.rfs and zImage using your favorite method.
That's it! Your phone will now boot and complain forevermore that the external memory is corrupt. ToDo: use third partition on external microSD as external_sd...
To recap:
We're telling android's init and whatever .rc scripts contain references to the broken partitions on the internal storage /dev/block/mmcblk0 to point to an appropriate partition on the external microSD card /dev/block/mmcblk1. You can actually do anything you want with the partition structure as long as it's consistent throughout init and in vold.fstab. Different ROMs do it differently.
I am not responsible for misuse of your hex editor, lack of backups, etc. I highly recommend the unbrickable mod.
Corrupt internal storage
Hi b0nafide,
My internal storage is also corrupted (i9000). I'm getting the same errors you descripe in your post. I'm trying your solution in wich you install android on your external SD. I bought a 8GB cat10 SD card....
But I'm stuck at the step: 'Extract initramfs from zImage ( [//github.com/mistadman/Extract-Kernel-Initramfs] )'. When I start the script nothing happens, except for my terminal closing. I'm using a virtualy installed Ubuntu distribution (Backtrack 5).
Do you have a tip? Perhaps you can help me through Teamviewer???
Hope do hear from you... I want to use my phone again
Greatings, Eldoro
My sgs is dead.
Please b0nafide, can you upload this modificated kernel (zImage and factoryfs.rfs) just for noobs like me?
Yes that woud be great. ..
Sent from my GT-I9300 using xda app-developers app
Here also an i9000 with reboot
Have done allot, stock rom, other pit files...
Is there a way to do this with a i9000 ?
and yes an image for us ?
and is the phone then normale... or is the internal storage still broken ?
Thanxs
Anyone can help us?
grimorct said:
Anyone can help us?
Click to expand...
Click to collapse
???
Anyone with working solution for this on i9000? I'll try to pack JW4 following this guide
grozni said:
Anyone with working solution for this on i9000? I'll try to pack JW4 following this guide
Click to expand...
Click to collapse
Yesterday, I made a flasheable pack of JW4, but it doesn't run. Now i'ḿ trying to modify JVU, but a strange thing happen when i'm repacking zImage...the script spends a lot of time in order to make it, and i can't be able to verify the correct pocess of new_zImage.
It's my first post in XDA, because normally I use HTCMANIA... I'm Spanish...and my English it isn't so good. Even, I should said that it isn't my phone...i'm repairing a friend's phone, so it's difficult for me to explain or speak about different ROMs or kernels....sorry
It's very important to advice that the scripts posted should be modified to get it run...because I found different problems to execute on Ubuntu.
Now it's 1:30 am...i'm trying "ext_JVU"....tomorrow i'll tell you the results.
Anyway i'll try to upload it, to reach different conclusions...
sesetxu said:
Anyway i'll try to upload it, to reach different conclusions...
Click to expand...
Click to collapse
Please do, I'll try flashing immediately and get back with results. How did you format external sd card?
I'm willing to try aswell... almost gave up hope.
Sent from my GT-I9300 using xda app-developers app
Hello friends!!!
I've the CODE (PDA file in ODIN) modified to execute android in ext-sdcard.
I do it as the first post said....but it doesn't run for me...
Anyway here is...Yo must get the MODEM and CSC os the stock firmware
XDA block the urls for me...for this reason its haven´t the WWW ...
Stock firmware..only to get MODEM and CSC: 4shared.com/zip/W1NeYAPA/I9000XXJVU_I9000OXAJVU_OXA.html?
Code modified to run in sdcard external: rapidshare.com/files/3786190721/ext_XXJVU.tar.md5
To solve my problems, i'll try to generate an CWMfile flasheable to try it...but now i'm hopeless....
Good luck men!!
sesetxu said:
Good luck men!!
Click to expand...
Click to collapse
Great work men!! It works for me. After flashing I got error in picture I posted (same error as before when writing to internal storage with stock rom). I just hit reboot but honestly I was not thinking it will boot. Thing I noticed when I start camera I get message turn off usb storage first. My files app shows no sd card inserted. How did you format your sd card? I'm using 8gb class 6 sd card
grozni said:
Great work men!! It works for me. After flashing I got error in picture I posted (same error as before when writing to internal storage with stock rom). I just hit reboot but honestly I was not thinking it will boot. Thing I noticed when I start camera I get message turn off usb storage first. My files app shows no sd card inserted. How did you format your sd card? I'm using 8gb class 6 sd card
Click to expand...
Click to collapse
I've modified all to use an sdcard with the folowing partitions:
1st primary fat32 which is internal sd card (4 gb)
2nd primary reiserfs which is /data (2 gb)
3rd primary fat 32 as external sd card
Try it...and I am happy to help you
sesetxu said:
I've modified all to use an sdcard with the folowing partitions:
1st primary fat32 which is internal sd card (4 gb)
2nd primary reiserfs which is /data (2 gb)
3rd primary fat 32 as external sd card
Try it...and I am happy to help you
Click to expand...
Click to collapse
I will try this layout. At first I prepared sdcard with 2 partitions which currently boot into Android but storage isn't working:
1st primary fat32 (6gb)
2nd primary ext4 (2gb)
You said raiserfs, should be that rfs type partition?
Update: I just noticed that both partition on my sdcard are fat32. First partition which should be internal storage I had to format again (not sure why). After this internal storage is still not available when in Android. I guess some mounting point is not good. Second fat32 partition is where the data is I guess (picture attached)
Exactly the same result as grozni. Same errors upon installing but booting into android. Amazing work! Also formatted 2 partitions. WiFi also not working btw. Hangs on obtaining ip...
Sent from my GT-I9300 using xda app-developers app
eldoro said:
Hangs on obtaining ip...
Click to expand...
Click to collapse
Same here
Is imposible to start Andoird without a rfs partition to mount /data (or ext4, for ROMs wich has fixed the troubles with ext4/rfs file systems...)
I can´t start the phone, because i get an added problem (my system can't format rfs data..but i don't know why)
I'm going to review the file /system/etc/vold.fstab who manages the mount points of the internal and external storages.
If anyone gets the correct configuration...please post it..
Tomorrow is Monday...and although I'm Spanish, I have a job (****ing crisis)...and i haven't so much time as weekend
Edit: wifi sockets are created over /data partition, if there is any problem in this partition is probably to get troubles obtaining IP
sesetxu said:
Is imposible to start Andoird without a rfs partition to mount /data (or ext4, for ROMs wich has fixed the troubles with ext4/rfs file systems...)
Click to expand...
Click to collapse
If I understand correctly samsung rfs and reiserfs are not the same thing? Why you use raiserfs on sdcard layout?
sesetxu said:
Edit: wifi sockets are created over /data partition, if there is any problem in this partition is probably to get troubles obtaining IP
Click to expand...
Click to collapse
That is the reason
Update: One more thing I forgot to mention. When I try to format USB storage (internal sd) I get message sd card removed
Hi,
I have a nook that I rooted and put a custom rom on back about a year and a half ago. I flashed the ROM to the internal EMMC and CWM 3.2.0.1 was flashed as recovery. If it makes any difference it was a CM9 ROM
Now here's where I'm at. I can run ROMs off the sd-card but they are not stable at all. I get a whole bunch of force closes and such.
When I try and flash a new ROM to the internal EMMC it says it completes, but nothing changes. It is still the previous ROM. When I try and format the /data and /system partitions with the EMMC recovery, it doesn't complete. It says there is an error. When I format with TWRP off an sd card, it says it completes but once again, the rom is not wiped.
I've tried the 8 reboot error method, and it never gets to the stock recovery screen. It keeps booting to the EMMC ROM.
I've tried repartioning the EMMC with leapinlar's zip files. It says it successfully completes, but once again nothing changes.
Ideally I'd like to get the emmc back to stock and try and run a rom off the sdcard.
I've read the threads that I thought were applicable to my issues, but nothing seemed to work. I'm completely out of ideas. Anyone have similar issues or can provide some guidance?
Thanks.
The problem you are having running a ROM from SD is the brand and speed of SD you are using. It needs to be SanDisk class 4.
The reason the 8 failed boot does not work is you replaced the stock recovery with CWM. It needs the stock recovery to be able to complete. See my NC tips thread linked in my signature and read item A12. Assuming you can get it to flash, I have a stock recovery zip there.
I don't understand why the ROMs are not flashing. You say it gives errors when you try to wipe with CWM. What do the errors say? You used the internal CWM and TWRP on SD, but none worked. Try my bootable CWM SD to see if that helps.
I don't understand why my partition zips did not work. I know the newest TWRP will not flash them without giving an error 2 message. Try my bootable CWM SD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Thanks for the advice...
I've been using a Patriot class 10 micro sd to run the roms/attempt to flash new roms. Its worked fine before, but I'll try and pickup another one from someplace.
When I try and format /system and /data from the emmc CWM it says "Error formatting /system" or "error formatting /data" after working away for about 5 minutes
Here's what i did:
Created CWM 6.0.1.2 Bootable SD
- Flashed NookColor-emmc-stockrecovery.zip
- Message said successfull.
- tried to restart and old CWM recovery 3.2.0.1 was still installed
Booted into CWM 6.0.1.2 Bootable SD Recovery
- mounted /system and /data
- attempted to format
- Message "Done." for both
- attempted to flash stock 1.4.3 that you have modified for CWM
- install from sdcard complete
- reboot
- Old CynanogenMod bootscreen and old rom still installed.
Using same CWM 6.0.1.2 Bootable Sd Recovery
-flashed NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip and NookColor-emmc-format-partitions-5-6-7.zip
-said success
-attempted to flash stock 1.4.3
- nothing changed. Old rom still installed
One more thing I noticed:
Everytime I login to the currently flashed rom, any changes I make are never saved. For example, if i install an apk or uninstall an app, the next time i can successfully boot into the emmc ROM, those changes are reversed to the previous version. Could it be that the current rom is being stored somewhere and being reflashed when it tries to bootup?
I hate to say this, but it sounds like your internal embedded card has become read only. I have had this happen to SDs but not to emmc. The apps act like they are writing and if you leave the folder and come back, they are not there. It is like they are writing to a ramdisk instead of your SD. You might try booting to a ROM on SD and see if you can write to any of the internal partitions like /cache or /rom and see if they stick. If not, you may only be able to run off SD and maybe not even then. You might have to change your dalvik cache setting on SD so it uses /data instead of /cache.
Sent from my Galaxy Tab running Tapatalk
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
canjoe said:
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
Click to expand...
Click to collapse
I don't know of anything that can revive it. I never could revive my SD that that happened to.
To make your ROM on SD use /data for all of the dalvik cache, create a file in /data named local.prop. In that file put this line:
dalvik.vm.dexopt-data-only=1
Next time it boots the system file portion of dalvik cache will be on /data along with the installed app portion.
Sent from my stock Nook HD+ using XDA Premium
I now have a stable version of CM 7.2 running off the SD card. I put the davlik cache on the data partition and everything seems to be running pretty smooth.
I'll keep messing around seeing if there is anything to revive the internal emmc, but at least I can use the nook off the SD card again.
Thanks for helping me troubleshoot and figure this out. Cheers.
I know there is a lot of information out here about the nook color not being able to boot but none of it seems to fix this issue. I was trying to upgrade my nook from cyanogenmod 7.2 to cyanogenmod 10.2. I used Rom Manager on the device and downloaded the new ROM. Everything was fine until I told it to install. The nook went to reboot and I was presented with a black screen. I couldn't get it to do anything and I thought it was dead forever. I then installed a bootable ROM on my SD card and was able to get it to boot from the SD card. I have attempted to install several different versions onto the EMMC but none will boot. When I reboot the nook it just goes to a black screen and sits there, even with the SD card in it. This is the only sequence that allows me to get my nook color to boot from an sd card:
1) Hold the "n" and power buttons for 30 seconds (I think this forces it to power down)
2) Push and hold power button for a few seconds.
If I do this with a bootable SD card installed the nook boots the SD card. If I do this without the SD card installed I just get a black screen. I have tried many things from many threads here. I have tried fixing partitions, installing new ROMS and other things but nothing seems to work. I know the nook is not bricked because I can boot it from the SD card. I think the boot partition may be the issue. When I am booted from the SD card I can mount all partitions except "/boot". Should I be able to mount this partition?
I just need to know how to get my nook back to a state where it will boot without the SD card inserted. I know how to create a bootable SD card and install zips.
Very frustrated at this point, guidance that anyone can give would be greatly appreciated...
Thanks.
You said you tried fixing partitions. How did you do that and what were the results? Were you using my partition repair zips from my partition repair thread linked in my signature?
And ROM Manager assumes you have a correct version of CWM installed on internal memory. It is best not to use that tool. It is way outdated. It is best to install ROMs manually with CWM.
Sent from my BN NookHD+ using XDA Premium HD app
deleted post
Partitoning did not seem to help
leapinlar said:
You said you tried fixing partitions. How did you do that and what were the results? Were you using my partition repair zips from my partition repair thread linked in my signature?
And ROM Manager assumes you have a correct version of CWM installed on internal memory. It is best not to use that tool. It is way outdated. It is best to install ROMs manually with CWM.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Yes I have done 2 out of the 3 zips you have on your post. 1) NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip and 2)NookColor-emmc-format-partitions-5-6-7-8.zip. I did not do the partition 2 zip as it looked like it may cause more problems. However, I'm not sure it could get much worse.
Today I ran the RecoveryFix.zip from this post --> http://forum.xda-developers.com/showthread.php?t=958748
No Help. Same issue, I reboot and nothing but a black screen. I have to do the 2 steps I described in my original post to get the SD card to boot. Is there a way I can see what is on the nook partitions? These tools allow me to copy zip files but there is nothing that allows me to look around on the nooks internal partitions. What does the nook need to boot without the SD card. It seems there must be something partially working because I can get the SD card to boot...
Thanks I advance for your help.
Need to fix internal hard drive...
Ok, so now I'm pretty sure it's just my internal memory that is screwed up. I installed CM 7.2 on an SD card and now my nook color is running from the SD card. But if I take the SD card out and try to reboot all I get is a black screen(Not even a flash or anything when hitting the power button). So right not the only thing my nook can do is boot from the SD card.
How can I fix the internal memory??
noooker said:
Ok, so now I'm pretty sure it's just my internal memory that is screwed up. I installed CM 7.2 on an SD card and now my nook color is running from the SD card. But if I take the SD card out and try to reboot all I get is a black screen(Not even a flash or anything when hitting the power button). So right not the only thing my nook can do is boot from the SD card.
How can I fix the internal memory??
Click to expand...
Click to collapse
Try flashing the repair partition 2 zip. It has protections built in to prevent further damage.
Then go to my NC tips thread linked in my signature and return to stock via item A15. Be sure to flash the format zip listed there too. Then you should be able to start over.
Sent from my BN NookHD+ using XDA Premium HD app
Repair Partiton 2 failed
leapinlar said:
Try flashing the repair partition 2 zip. It has protections built in to prevent further damage.
Then go to my NC tips thread linked in my signature and return to stock via item A15. Be sure to flash the format zip listed there too. Then you should be able to start over.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Ok, I think I may have totally screwed this nook up. I found some other repartition//format zips that I ran trying to fix the problem. Now I can't even run from the SD card. It tries to boot but I get an error and it fails. I tried to run your repairpartition2.zip file but it did not work. This is the output:
E:Can't mount /cache/recovery/last_install
E:failed to open last_instal: no such file or directory
Finding update package...
Opening update package...
Installing update...
Repair /rom partition (P2)
Checking for /factory - if ot found will return error message and repair will be aborted.
assert failed:mount("ext2", "EMMC", "/dev/block/mmcblk0p3", /factory") == "/factory"
E:Error in /sdcard/NookColor-emmc-repair-partition-2.zip
(Status 7)
Installation aborted.
I've also noticed that it cannot mount any of the partitions from the booted SD card any more. I'm seeing
E:Can't mount /cache/recovery/log and other errors
I think one of the other .zips I ran screwed things up even more. Am I now screwed up past the point of no return? I have very good unix knowledge but very little android knowledge. Is there anything I can do with the adb utility to help here.
Thanks for all your suggestions so far. It seems like I need to redo this thing from scratch and need some guidance on how to do it.
More Info: Now when booted from SD card I cannot mount "/boot", "/system", "/data", "/emmc" or "/cache" partitions. I wish I could get a shell and look around on the rom...
noooker said:
Ok, I think I may have totally screwed this nook up. I found some other repartition//format zips that I ran trying to fix the problem. Now I can't even run from the SD card. It tries to boot but I get an error and it fails. I tried to run your repairpartition2.zip file but it did not work. This is the output:
E:Can't mount /cache/recovery/last_install
E:failed to open last_instal: no such file or directory
Finding update package...
Opening update package...
Installing update...
Repair /rom partition (P2)
Checking for /factory - if ot found will return error message and repair will be aborted.
assert failed:mount("ext2", "EMMC", "/dev/block/mmcblk0p3", /factory") == "/factory"
E:Error in /sdcard/NookColor-emmc-repair-partition-2.zip
(Status 7)
Installation aborted.
I've also noticed that it cannot mount any of the partitions from the booted SD card any more. I'm seeing
E:Can't mount /cache/recovery/log and other errors
I think one of the other .zips I ran screwed things up even more. Am I now screwed up past the point of no return? I have very good unix knowledge but very little android knowledge. Is there anything I can do with the adb utility to help here.
Thanks for all your suggestions so far. It seems like I need to redo this thing from scratch and need some guidance on how to do it.
Click to expand...
Click to collapse
That error message says your factory partition is gone and it contained info there that is vital and un-retreivable. You might be able to rebuild your partitions but some ROMs will never run without that backup info from /factory (partition 3). You just got too aggressive with your partition repairs.
Sent from my BN NookHD+ using XDA Premium HD app