Related
First off, I need to address credit where credit is due. All credit goes out to Samuelhalff, Nootered, thecubed, iomonster, Decad3nce and anyone else involved with any of the methods I will mention.
As always, everything in this guide is completely at your own risk, I am not responsible for you messing up your device further nor am I responsible in the event that your Nook Color explodes and kills your cat, grandma, etc.
The Fatal Black Screen:
This is the issue where your Nook "refuses to boot up" usually after running Froyo (or possibly HC) off of your internal memory. This is usually caused by, but is not limited too, formatting your sdcard from within Froyo (or versions of HC prior to the flashable zip).
99.99% of the time, this does not mean your Nook is bricked in any way, what simply happened is your boot partition has become corrupted. For you newbies out there, the boot partition is what allows your Nook Color to turn on. The boot partition contains the instructions for what your Nook Color needs to do in order to start up and run.
The Fix:
Thanks to the guys that developed this neat toy, the Nook is set to boot from the sdcard before booting from the internal memory. What this means is, your nook will first search for a boot partition on the sdcard before searching for a boot partition on your Nook's internal memory. Because of this, we are able to boot and run OS software directly from the SDcard. This is how we will be fixing your "bricked" Nook Color.
First visit this link:
http://forum.xda-developers.com/showthread.php?t=922870
Download either the Rootpack, or the Clockwork Recovery image (1gb).
Next visit this link and download the 1.0.0 or 1.0.1 restore to stock files:
http://forum.xda-developers.com/showthread.php?t=914690
From this link you should also download the very last zip on the page. It is titled-flashable boot repartition zip. or something of the like. If you followed all these steps and still nothing, I would recommend flashing this as it can fix a completely screwed boot partition.
If you wish to instead restore to a pre-rooted 1.1, visit this link:
http://forum.xda-developers.com/showthread.php?t=932145
Once you have the either version of the bootable Clockwork Recovery (Rootpack or normal standard Clockwork Recovery) and a software version you would like to restore to, you must write your clockwork recovery to an sdcard to make it bootable in the Nook.
In order to do this, you must use Win32DiskImager on Windows or the command line on Mac and Linux. Follow theses instructions for writing the file to an sdcard (substitute the Clockwork file in place of Nooter):
http://nookdevs.com/NookColor_Rooting
Once the image is done writing, open up your sdcard on your computer and copy whichever restore to stock zip you choose earlier onto the card.
Now with your Nook Color unplugged from the computer, insert the sdcard and plug the Nook into the computer. Your screen should flash to life. After a short loading screen you will see a menu, using the volume keys, you are able to navigate up and down. Navigate down to the menu item that reads "mounts and storage." Navigate down and press "Format Data" then "Yes." Next do the same thing except format system. Using the power button to go back to a previous menu, return to the "mounts and storage" menu, make sure the sdcard is mounted. (If your sdcard is mounted, you will see the option to 'unmount /sdcard'. If it is not mounted you will see 'mount /sdcard'. In this case you would want to press the 'mount /sdcard' option in order to mount it. Again using the power button as the back button, navigate back to the main menu. You will see a menu item that reads "Install zip from sdcard." Select it. Now select 'choose zip from sdcard.' Now pick the zip you placed on the sdcard earlier. Scroll down to the 'Yes' option and select it. Clockwork Recovery will begin flashing the stock image to your internal memory. After a few minutes, the process should complete and you will see a message that says 'Done. Installation Complete.' From here you should remove your sdcard and navigate back to the main menu. Select the 'Reboot Now' option.
Note: Sometimes after you see the 'Done. Installation Complete.' message, Clockwork will freeze up and you will be unable to navigate back to the main menu in order to reboot. If this is the case do a hard reboot (hold the power button for 15 or so seconds so the screen turns off, then hold the power button again till it turns on).
Congratulations, you've unbricked your bricked Nook Color
TO EVERYONE STILL HAVING PROBLEMS AFTER THIS, YOU MAY/SHOULD FLASH SAMUELHALFF'S REPARTITION ZIP MENTIONED EARLIER. (LOOK UP A FEW LINES, SAME LINK AS THE 1.0.0 AND 1.0.1 RESTORE TO STOCK ZIPS)
UPDATE:
IF YOUR STILL HAVING PROBLEMS, USE THIS LINK TO INSTALL 3.0.1.0 ON INTERNAL EMMC AND THEN BOOT TO IT.
http://forum.xda-developers.com/showthread.php?t=958748
note: to do this, you need to be able to atleast boot to the N screen.
MORE UPDATE:
This link has an updated bootable CWM version on it with ext4 support. Write this to your sdcard, format /system and /data and flash CM7.
http://forum.xda-developers.com/showthread.php?t=959240
If anyone has anything to add to this tutorial, post here or IM me and I will edit the OP.
So I was doing the 'restore to stock' method earlier today and accidentely reformatted my boot partition is there a fix for this or am I completely hosed now?
bartimeus said:
So I was doing the 'restore to stock' method earlier today and accidentely reformatted my boot partition is there a fix for this or am I completely hosed now?
Click to expand...
Click to collapse
Not hosed at all, all you did was format the internal boot partition. When you insert the sdcard and turn the power on, your Nook will find the boot partition on the Clockwork Recovery sd card and boot to that, enabling you to do a full restore.
Well then there may be something more wrong with my nook. I have performed this 3 times and I am still just stuck at a blank black screen.
Are you sure you wrote the image to the sdcard right? Have you plugged in your nook and let it sit for a while? The Nook does have a pretty strange way of running its battery completely dead. What OS were you running before you went to restore to stock?
bartimeus said:
So I was doing the 'restore to stock' method earlier today and accidentely reformatted my boot partition is there a fix for this or am I completely hosed now?
Click to expand...
Click to collapse
Yes, it is totally effed. Just send me the nook, it's garbage now anyhow.
nootered said:
yes, it is totally effed. Just send me the nook, it's garbage now anyhow.
Click to expand...
Click to collapse
lmfao .
Oh dear god this just happened to me today. Thank you for posting this up.
nootered said:
Yes, it is totally effed. Just send me the nook, it's garbage now anyhow.
Click to expand...
Click to collapse
lolololololololololololol
Sorry. But if the boot partition is corrupt these files wont suffice. You'll need to flash my boot repartiton zip..
Sent from my HTC Desire using XDA App
Hi, thanks for putting this topic up and of course full credit goes to everyone who's been so helpful replying to bricked NC posts.
After 4 days of searching and trying to revive my bricked NC (tried the conventional 8 reboots, power+n methods), I believe I have a unique situation where I:
1) Can't load 128MB/1GB CWR SD ('loading' word appears, then black screen of death appears)
--tested a variation of power + n + up/down arrows (for 2-3mins or more)
--used PC USB / AC to turn device on
--used a Sandisk 256MB/2GB/4GB-CL4 and Transcend 8GB-CL6 uSDs
--used Win7, Ubuntu, EASEUS Partition Master, SD Formatter and another Android device to format the uSDs
--burned the .img using both Win32DiskImager and WinImage
2) Can't load any Froyo/HC SD roms (same results as above)
--same conditions as above
--plus tried every available version of NookieFroyo/HC out there
3) Can't access ADB at any given point. devmgmt.msc does not show any hardware with any VID of 2080. When the NC is powered on by USB, windows detects it and chimes, but that connection disconnects instantly.
Simply put, how it happened was:
OOBE -> BN 1.01 -> Autonooter -> block OTA -> Root + gApps > Rom Mgr'd CWR into eMMC -> HC v4 SD -> gApps -> manual su -> dalingrin's 1.1ghz oc kernel -> reboot success > checking on symlinks -> sudden auto-reboot to stock -> reboot done -> HC loads ok -> blacks out, unable to reboot anymore.
Has anyone else encountered this scenario? In my searches I've not come across anyone with this failure. Is it possible that my CPU has fried due to the OC to 1.1?
P.S. Sam, not able to try your methods as I'm not able to even boot anything from the SD.
I'mm in the same boat (nook) tried everything here as well as a similar guide on androidtablets and nothing. I can't boot at all. No power on, just a black screen. Any help at all would be welcome.
samuelhalff said:
Sorry. But if the boot partition is corrupt these files wont suffice. You'll need to flash my boot repartiton zip..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Ya, I realized that I forgot that, I'll add it in when I get home today, Thanks.
I flashed the 1.1 CWR image and all is fine now.
RileyGrant said:
Ya, I realized that I forgot that, I'll add it in when I get home today, Thanks.
Click to expand...
Click to collapse
The second link in your original post has a link to it as part of step 5.
It took a couple times of me re-writing the CWR image before I could get it to boot. Now I have it booting into CWR but when I flash the 1.0.1 recovery the nook refuses to boot. Any ideas?
edit: I am removing the micro SD before I reboot
edit 2: sam's repartition boot FTW....I think
LocalStain said:
I'mm in the same boat (nook) tried everything here as well as a similar guide on androidtablets and nothing. I can't boot at all. No power on, just a black screen. Any help at all would be welcome.
Click to expand...
Click to collapse
Glad you found this, it was my next recommendation after the charge break.
Sent from my LogicPD Zoom2 using Tapatalk
How about a dummies guide to the dummies guide for the dummies?
Or, better, WTF! ITS BRICKED!
Already did all the things suggested. Twice. Purchased last Nook Color from Best Buy yesterday, brought it home, charged it to 100%, played with it and ran Auto-Nooter 2.12.25. When I plugged in the cable to boot, it came up with the battery low-wait 15min screen. (Battery was at 100%) Tried again, same thing. Re-flashed Auto-Nooter and tried again, black screen. Nothing. Bricked. What I do get is a black screen with a flash of backlight every 20 seconds or so. Tried to re flash Auto-Nooter and boot, nothing.
Today same story, just wasted 5 hours trying: Auto-Nooter, Clockwork Recovery image, Nookie-Froyo, complete restore-1.0.1.......nothing brings up any life in the nook.
Suggestions? (Ready to return......)
Cant boot to SD
I am running the HC v4 flashed rom and I have tried numerous .img files. It is like it doest see the boot image I just created and boots into Honeycomb everytime? Any thoughts or help please sorry I am a noob.
< snip >
RileyGrant said:
Clockwork Recovery will begin flashing the stock image to your internal memory. After a few minutes, the process should complete and you will see a message that says 'Done. Installation Complete.' From here you should remove your sdcard and navigate back to the main menu. Select the 'Reboot Now' option.
Click to expand...
Click to collapse
< /snip >
After spending the better part of four hours trying to solve a fatal error with my reverted-to-stock NC, I ran across the fix for the problem.
First of all, the problem: After diagnosing a bad NC USB cable that was causing USB device mounting issues within Windows, I began to encounter a fatal error modal dialog that stated, "Your NOOKcolor encountered a problem that requires a system restart" at the home screen. No matter what I did in terms of formatting & re-imaging, the message remained. In an effort to fix it, I decided to restore to stock 1.1 using a bootable CWR SD image. After following the instructions to the letter, including formatting /System and /Data after shooting the stock 1.1 image onto the NC, the message persisted. I then attempted to back-rev to 1.01 and 1.0, with similar results.
I suspect that what happened to me was that during the process of diagnosing the USB cable issues, I booted from a uSD card that had AutoNooter 3.0 on it, and interrupted the process mid-stream, thus causing data or partition corruption. I'm not a Nook expert, so I'm not certain of this, but based on my general experience level, that's what it 'felt' like.
How did I finally recover? As a last step to the standard revert-to-stock process, after rebooting from CWR, I used a three-finger salute to reset the device. It was only after I did this that the fatal error disappeared.
Just thought that I'd post this in case anyone has a similar experience and is desperate for something else to try.
DS
I've gone thru the paces numerous times, even rolled a rooted install back to a full install of 1.0.1 and reapplied the HC v.4 (following all instructions carefully). I don't have any problems with the file extraction and get the Done message. However, when I reboot the nook it gives me a Loading screen then flickers a few times and then an ANDROID_ (flashing curson) and hangs. I've gotten this far every time I've tried to apply the zip. Once in awhile it will flash between the Loading and ANDROID_ screens a few times but ultimately I end up with ANDROID on my screen and nothing else.
Any ideas or direction I can move in? I'm anxious to try this out but prefer to run it from internal memory instead of an SD card...
There does seem to be one disparity between the instructions and the actual application of them, there doesn't appear to be a way to unmount /boot that I recall, only format it.
Make sure data and system have been formatted without issues before flashing the zip.
If that doesn't work, you might have a system partition size issue. Download shad0wf0x's stock image and dd it to your mmcblk0p5 partition (see specific thread). Then try flashing zip after having formatted both data and system.
Sent from my HTC Desire using XDA App
During the formats I haven't gotten any error messages, just a simple Done. when the format of each completes. I do hang when boot is done but a hard reboot, per the instructions, allows me to continue from there and I making sure /system and /data aren't mounted.
I'll give this a shot and let you know how it works out.
Thanks.
That didn't seem to do the trick. The last time I did this I started from a complete reinstall of 1.0.1 with an image I got from this thread.
http://forum.xda-developers.com/archive/index.php/t-914690.html
I'm able to boot into the stock install without difficulty, register the nook, setup my gmail association and then root. If I had a corrupted systems directory would I be able to do all those things?
Hello,
With the issues I was having with the CM 10.1 nightlies, much as I would like to stay, I decided to install the Minimoto 1.7 ROM into the second ROM slot (created with Safestrap 3.05). First, let me say "wow!" I never thought I would see this much speed and available RAM on my Droid 3. Thank you very much, thingonaspring.
For the most part, everything is working great *except* access to both the sdcard (internal) and sdcard-ext (external) storage areas. I read many posts in the Minimoto thread and searched around but nobody else appears to have encountered this which I find rather odd.
After the initial install and after reboots, these areas were still not accessible. I finally ran the terminal emulator and found that, for some unknown reason, they were *not* mounted. I *did* find the internal storage (/dev/block/emstorage) mounted at /ss but not at /mnt/sdcard. I became root using "su" and did the following:
# mount /dev/block/emstorage /mnt/sdcard
# mount /dev/block/mmcblk0p1 /mnt/sdcard-ext
Now I can access them along with all of the files I previously had there. The included file manager, when started, presents buttons for "Internal Storage" and "SD", but it still complains that internal storage is not mounted. It will allow me to access the SD card, though.
Under Settings->Storage Settings, everything under "Internal storage" and "SD card" says "unavailable" and both the mount and format buttons are grayed out. Yet, under the "Windows Media Sync" heading, I *can* choose between internal and SD *and* it even shows the correct available/total space values.
Why were these not mounted to begin with? Is mounting them manually an acceptable solution? If it is, where do I put this information so that it occurs at boot like it should (there is no /etc/fstab on Android)? Did I perhaps do something wrong when installing this ROM, maybe because I used ROM slot 2 instead of 1 (which still contains the most current CM 10.1 nightly)?
I really want to get this resolved because, so far, everything else appears to work wonderfully. Even 3g access, which I still haven't gotten working with CM 10.1.
--John Gruenenfelder
I've been running Minimoto for months and both /sdcard and /sdcard-ext are mounted at bootup for me, always, just like stock.
So, I wish I could tell you why, but I cannot.
I guess what I would do is start over. Reboot into Safestrap, remove that second slot and recreate it. Flash the ROM and restart the phone. Do not wipe data/factory reset after flashing the ROM or you will be missing some files (basically, some files required by the customized initial setup application.)
It seems to be fixed! See below for (perhaps) how...
Okay, I gave this a try. Rather than wiping ROM-slot-2, I had enough free space to create slot-3 and I reinstalled Minimoto 1.7 there. Also, this time I downloaded the zip file on my PC and transferred it over rather than downloading it directly onto the phone. Using the UNIX "cmp" tool told me the two files were identical, but I still used the "new" one. It installed fine and I did *not* perform a data wipe.
Unfortunately, same issue. When the device starts I can see the "Preparing XXX storage" messages appear in the notification bar for both internal and SD storage. There are no error messages, but it also did not actually do anything. Then, using the terminal emulator, I gave a long read through the dmesg output. I am more familiar with the kernel messages one sees when booting Linux on a PC, but I still did not see anything unusual.
So, back into Safestrap recovery. This time I tried something different. First, I noticed that the Safestrap file manager *can* see both storage areas and in the locations where they ought to be. This is not new, actually, it has always been the case. Second, I uplugged the USB cable. I have been using it for charging (of course), but at present it was plugged into my laptop and not into the wall charger. Depending on how the mounting occurrs and the exact mount order, I thought this might interfere. Thirrd, and finally, I used the "Fix Permissions" button available in Safestrap on ROM-slot-2 where I had first intalled Minimoto.
After doing these two changes I rebooted the device back into ROM-slot-2. Surprise! I once again saw the "Preparing" messages in the status bar except this time it really worked. The two storage locations are available where they should be and I an access the data just fine. Even the "Storage properties" screen in Settings shows both as mounted with the correct available/total space values given.
Since a plain reboot did not work previously, I have to assume one of the two changes I made fixed the problem, though, since I did both at the same time, I cannot be sure which fixed it.
Now I can get back to enjoying the impressivee speed from Minimoto while I wait to see if (or perhaps when) either the 3g or HW keyboard ALT-key issues are fixed in CM 10.1. Of course, given how much slower CM 10.1 operates (by virtue of using *much* more RAM than Minimoto), I think I might find it very difficult to switch.
--John Gruenenfelder
If you've been trying to hoot while plugged into your laptop I can see it causing issues as when usb mass storage is active, the device can no longer see the sd cards. That is why we have a separate data partition for apps and app data. So if the computer is trying to mount them and denies the phone the ability to mount then I could see issues arising
Sent from my XT860 using xda premium
Hi all
For days I've been flashing all different kinds of things in hope to get my phone fixed, but I just can't find the answer.
So for those of you most kind enough to help, here's what's going on with my captivate (at&t)
I took it out of my pocket last week and the phone was frozen. Sometimes it happens... a quick pull out of the battery and re-insert fixes it in most cases... but not this time.
After restarting the phone was hanging on boot screen (CyanFox bootscreen).
I restarted... 15 minutes on that bootscreen still. I had no idea what was going on.
So I decided to reflash. It was a big decision, seeing as this ROM has been working absolutely fine for weeks, but I needed to get it working.
Soon after getting it into recovery, CWM was saying that it couldn't mount /sdcard
I tried even flashing using Odin to go back to stock following the guide here: http://forum.xda-developers.com/showthread.php?t=1300843 still not working.
Most of them ended up showing that little android loading bar for a second or two, but then get stuck in a boot loop.
I tried flashing many different kernels, and different recoveries, but everything all pointed towards: Unable to mount /sdcard
But alas, finally I found something that more or less works. I flashed the Initial Kernal for Cognition: http://forum.xda-developers.com/showthread.php?t=1127578
And I finally got back into a working device... or so I thought.
The phone is still unable to access the internal SDCARD. Just says 'unavailable'. I tried putting in an external 2GB sdcard, but that reads as Total Space: 00, and Available Space: 00
The external sdcard I know works, because my wife's samsung mini2 reads it just fine.
Multiple formats and it still can't be read.
I tried plugging in the device into my pc and select mass storage, but although the computer detects that the phone is plugged in (in device manager) the 2 drives for internal and external both remain hidden, and cannot be accessed.
I have absolutely no idea what to do next. I've used Odin and Heimdall, Repartitioned, and followed every stickied guide here, but I still can't find what to do.
I really appreciate any help anyone can give me on this.
Just for the record, ADB works just fine from my PC. I can send the commands to the device, but mounting the sdcard still proves impossible at this stage (no file exists).
Thanks again, I look forward to any advice anyone can spare.
flapsy said:
Hi all
For days I've been flashing all different kinds of things in hope to get my phone fixed, but I just can't find the answer.
So for those of you most kind enough to help, here's what's going on with my captivate (at&t)
I took it out of my pocket last week and the phone was frozen. Sometimes it happens... a quick pull out of the battery and re-insert fixes it in most cases... but not this time.
After restarting the phone was hanging on boot screen (CyanFox bootscreen).
I restarted... 15 minutes on that bootscreen still. I had no idea what was going on.
So I decided to reflash. It was a big decision, seeing as this ROM has been working absolutely fine for weeks, but I needed to get it working.
Soon after getting it into recovery, CWM was saying that it couldn't mount /sdcard
I tried even flashing using Odin to go back to stock following the guide here: http://forum.xda-developers.com/showthread.php?t=1300843 still not working.
Most of them ended up showing that little android loading bar for a second or two, but then get stuck in a boot loop.
I tried flashing many different kernels, and different recoveries, but everything all pointed towards: Unable to mount /sdcard
But alas, finally I found something that more or less works. I flashed the Initial Kernal for Cognition: http://forum.xda-developers.com/showthread.php?t=1127578
And I finally got back into a working device... or so I thought.
The phone is still unable to access the internal SDCARD. Just says 'unavailable'. I tried putting in an external 2GB sdcard, but that reads as Total Space: 00, and Available Space: 00
The external sdcard I know works, because my wife's samsung mini2 reads it just fine.
Multiple formats and it still can't be read.
I tried plugging in the device into my pc and select mass storage, but although the computer detects that the phone is plugged in (in device manager) the 2 drives for internal and external both remain hidden, and cannot be accessed.
I have absolutely no idea what to do next. I've used Odin and Heimdall, Repartitioned, and followed every stickied guide here, but I still can't find what to do.
I really appreciate any help anyone can give me on this.
Just for the record, ADB works just fine from my PC. I can send the commands to the device, but mounting the sdcard still proves impossible at this stage (no file exists).
Thanks again, I look forward to any advice anyone can spare.
Click to expand...
Click to collapse
i had the same problem a couple of weeks ago...
you internal sd card is dead...
you can do nothing about it for now...
if you want to confirm open your camera app and see if you can take any pictures...
if no, then follow the things as i say..
this requires you to do a partition of your external SD card and to that it should be formatted, so take the neccessary backups..
1) download this http://www.mediafire.com/download/sbjd049x4m36pb6/I897UCKI2_noBL_BoogsKernel.rar
2) after flashing this stock firmare with cwm, open up the recovery.
3)follow this guide http://forum.xda-developers.com/showthread.php?t=1447303
4)i couldn't get ICS to work..
5)so you can now use kitkat roms only on the captivate as we have the kernel for 4.4 only with swap sd
6)so after you follow the guide and boot into ICS, copy the rom.zip which you want to flash and the neat kernel swap sd, which can be found here http://www.mediafire.com/download/s34o69u39u66x8n/NeatKernel_v1.03-[02-08]-cma-swap-captivate.zip, be sure to thank the developer here http://forum.xda-developers.com/showthread.php?t=2548081
7)so flash the kitkat om which you want to use,and then flash the neat kernel after flashing the rom after that you can flash the gapps and reboot..
if you do everything like i said, your cappy will be up and working again..
Sir, you are a gentleman and a scholar
Although it didn't go exactly as planned step by step, with your instructions I finally managed to get it working on my 2GB external card.
Here was the process I did
1) Downloaded CM11, Gapps, Stock Kernal and the SwapSD kernal you linked
2) Flashed the stock kernal, the phone just went on a rebooting spree.. but after a few attempts I got it into recovery using the 3 finger combo
2) Followed the instructions on http://forum.xda-developers.com/showthread.php?t=1447303 to partition the external SD card. (Since I have only a 2GB card, I partitioned 1GB for data, and 0MB for swap)
3) Done the classic wipe sys/ cache/ data
4) (Here is where things changed a bit for me, as I couldn't boot into ICS either. And no other rom would work at this point) I installed the new SwapSD kernal to get a newer version of CWM by mounting USB storage via CWM and copying the files to there.
5) The device rebooted a couple of times during install, but it automatically went straight back into the newer CWM.
6) Installed CM11, let that finished and installed Gapps straight after.
7) Rebooted and the phone is now reading my external sd card as its internal storage, which is fantastic
Although with it's limited storage and broken internal storage, it still needs replacing, but at least I now have a device from which I can still run a few apps on regardless.
So thank you again dude
*edit* just need to figure out why the adb drivers decided to not work anymore.
Sometimes I hate having windows 8...
Hello,
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2
I see it's been a couple weeks with no update but if you're still stuck this may help. I had similar issues trying to flash zips from recovery. I kept getting the "can't mount" error message and what I figured out is that the access to CWM recovery via the update method I'd used was pretty much loaded up in cache, thus I couldn't mount . Getting back to total stock first may help. This is the basic rundown I performed to get my cappy back up ... currently on JB. Granted, I didn't go about reformatting drives as you did.
1. Flash I897UCKK4 with Odin (no root) for gingerbread stock rom
2. Download and install KK4root. Run Kk4 root "run" exe in the kk4_root folder. Corn kernel is installed with modded recovery system
3. From Corn kernel recovery click "root extras" to get su and busy box installed
Everything is pretty much dependent on using them in Windows and still active in download links if you do some searching.
Hope it helps!
Aimless Rambler said:
I see it's been a couple weeks with no update but if you're still stuck this may help. I had similar issues trying to flash zips from recovery. I kept getting the "can't mount" error message and what I figured out is that the access to CWM recovery via the update method I'd used was pretty much loaded up in cache, thus I couldn't mount . Getting back to total stock first may help. This is the basic rundown I performed to get my cappy back up ... currently on JB. Granted, I didn't go about reformatting drives as you did.
1. Flash I897UCKK4 with Odin (no root) for gingerbread stock rom
2. Download and install KK4root. Run Kk4 root "run" exe in the kk4_root folder. Corn kernel is installed with modded recovery system
3. From Corn kernel recovery click "root extras" to get su and busy box installed
Everything is pretty much dependent on using them in Windows and still active in download links if you do some searching.
Hope it helps!
Click to expand...
Click to collapse
Thanks for the reply; I constant checked this site for a week or so with no response, so I gave up. I would have been able to go with your method if my download mode worked. Basically, I cannot go into either download mode or fastboot. I tried to flash different kernels to try to enable it, but I kept running into error 0 even after I changed the binary. Any idea? Thanks.