Related
Hi everyone,
In my overzealous attempts to reformat an old 4gb external SD card through CW Recovery, I managed to reformat my internal SD card (I was using the Clockwork Recovery version 2.5). I thought that "format sd card" would reformat my external memory card and not leave me without a usable phone, but I guess I misunderstood.
I spent at least five hours going through all of the ODIN tutorials and trying them out, and found that using Eugene's 2.2 with 2E recovery ROM actually allows me to boot up (hooray! ), while the stock rom from this thread simply forces a bootloop on my poor phone, with occasional freezes. Even using AIO's "Flash to Stock" from Eugene's 2.2 doesn't work.
Further searching has lead to the thread about partitioning using parted, which has been hard for me to use effectively (I made a new partition, but I couldn't get it to mount properly).
I was really excited to come across this tutorial, but it didn't solve my problem. After getting through all of the steps, at step 5, ODIN3 versions 1.0, 1.7, and 1.81 (I tried all 3 on 3 different walk-throughs of the tutorial) never were actually capable of repartitioning the sdcard properly. Every time after the first time of using "parted" to reduce the card to a single partition, I found that that lone partition was always the only one there (15.5 gb /SYSTEM Fat32). No changes had been made to the sd card's partitions.
I don't know if it helps any, but the ROM I was running before I reformatted the card was Bi-Winning 3.0, and Voodoo had not been disabled at the time of the reformat, which may be why I can't flash new ROMs through the recovery as well.
As near as I can tell, ODIN can't actually return my vibrant's partitions to factory settings, so is there a way for me to do that manually? I think that would solve my problem.
Thanks,
-NewbieCube
My guide (you linked to) clearly states its not for this intent... if you read it, you would also see I linked to Eugenes froyo that does not brick. If you did it, THEN you did my guide ODIN to JFD, you are on a fully functional stock 2.1 JFD build.
If your intent was to just format the external sd, go to menu settings, sd card/phone storage, unmount the external and format it.
Right, I know that. In fact I read all through your thread and tried to flash to Eugene's first, and then to JFD, but JFD does not boot properly. It just gives me a black, unresponsive screen. I'll definitely go back through once more and try that again, though, as you clearly know what you're talking about.
I basically formatted the wrong storage (internal sd vs external sd), and would like to get that internal back to stock, so you are right that Eugenes -> JFD should work. I'll report back with results.
^ yeah, exactly... that should work with no issues. let me know if it does not.
Oddly enough, that didn't work for me either. Since my phone still can boot into Eugene's (albeit with 0.00B available to apps), I know this should work, just from reading through your guide. So once more, here's what I did:
1. Download mode -> ODIN 1.70: Flash Eugene_2E_JK2_Froyo.tar.md5, and s1_odin_20100512.pit (from Eugene) Re-Partition NOT checked (Eugene's thread says not to)
2. Boot up into Unbrickable Froyo, with no application space remaining Mount sdcard and move Update.zip (s15274n's) into the root folder without issue.
3. Download mode -> ODIN 1.70: Flash s1_odin_20100512.pit, and T959UVJFD.tar (s15274n's) with Re-Partition checked
4. Boots once automatically into recovery, saying something about a failed MBR checksum and failure to clear userdata
5. Bootloops that never get past the VIBRANT logo screen
6. Boot into recovery and try deleting user data and cache data manually and to reinstall packages, but bootloops continue.
I really don't know what I'm doing wrong here...
UPDATE:
I even used Heimdall on another computer and got the same result, so it isn't ODIN. Why is reformatting the internal SD card to stock so difficult to do?
delete my post
I FIGURED IT OUT!!! ...by random chance
For my problem, it was indeed the voodoo lagfix that was messing things up, and this post:
http://forum.xda-developers.com/showthread.php?t=888084
helped me out tremendously.
Hi folks!
I'm having some sort of issue with a corrupt partition/SD card and need a little direction.
I'm stuck with the tablet stalling upon boot after birds/g-tablet screen (it doesn't loop back, so I'm not sure this is strictly the infamous loop issue).
Typical restore methods via APX (NVidia flash, FORMAT) result in no change from above.
Trying to format data, re-partition, and some other clearing methods via clockwork mod, but most of those (except wipe cache) SEEM like they stall out (unless they are just taking way more time than expected and CWM isn't indicating progress well, but the "please wait..." instructions run well into the 30-60 min range, before I've given up on them.)
When I mount to my PC, windows suggests there are issues with the drive and interaction is funky (can't delete/copy to it successfully).
I'm guessing I need to leverage some sort've ADB to fix the partition/clean up corruption, but I'm not very familiar with those, so suggestion on where to get started there (or anything else) would be appreciated. I suppose it could be hardware related, but based on the "unbrickable" reputation, I'm hoping there's a way to rescue.
Are you still running a stock rom or have you installed a modded rom?
Stock?
In most recent successful version, I was running Cyanogenmod7, but have made several attempts since to restore to stock via NvidiaFlash (which processes up to the boot problem). Thanks!
Nvflash will not be able to fix a corrupt SD card. Please see this post for why not. A factory reset, or, a format internal SD card using ClockworkMod is what you have to do to fix SD card corruption problems.
Also read through this thread. Do you have the same problem as user jroger0707? I need more info. from you to make a determination.
Boot into ClockworkMod recovery, connect to the tablet using the USB cable and send me the dmesg.txt resulting from this command:
adb shell dmesg > dmesg.txt
Alright so here's the backstory. I bought a Vibrant off of ebay that was stuck in a bootloop. I thought to myself, hey I could just shove this thing into download mode and be on my merry way!
Well, I attempted to flash JFD with a jig that I had. Went fine, Odin gave it a PASS.
Still boot looped.
So I then try Eugene's no brick, and after finally getting the right version, it booted up. Then tried to flash to JFD again.
No dice.
Following the directions here I was able to finally get 2.1 to boot, now here is the problem that I'm currently stuck on.
I can't get the internal sd (onboard flash) to mount in the system. If I am at the shell I can browse to /mnt/sdcard and see everything on the phone and on the sd (external_sd).
But when I go into the settings, all I see is space unavailable and the format is grayed out.
The culprit I believe lies in the partition on the internal memory that creates this MBR checksum error every recovery.
Thoughts? Opinions? I know this can be fixed, I've come this far!
Below I've attached some of the voodoo logs, it seems that when trying to make the ext4 partitions, it can't find it. (I was trying this so I could in the end disable it)
Does anyone know what might be going on? Any tips at all?
The only thing that I can figure now is that there might be damage or the internal storage. When looking in /dev/block, there is no reference to mmc anything, like the internal storage isn't even there. Is the flash chip soldered on the motherboard? I'm guessif that it is, which means it would be a difficult fix.
Only other "solution" that I could thing of is if I mod the fstab to mount a microsd as the internal storage. Would this mod be affected by a flashing rom or odining back to stock?
Also is this the right board for this? If not can anyone direct me to the best spot to ask this question?
Thanks a bunch!
Please find my guide on the developers thread and follow it,
You will be bak at no sweat.
Any problems post there.
for this fix, you will need to have a CWM sdcard ready and waiting followed by and drivers properly installed for your tablet.
YOU MUST have CWM running from sdcard to fix this issue. Otherwise nothing will happen.
instructions to install to sdcard are here (I suggest using windows)
Needed files for download:
just download this zip and run the script while booted into cwm from sdcard.
download it here.
Instructions: Boot from sd (don't worry, it will work), ensure sdcard is mounted, and then you just run the fix.bat from the computer after extracting.
Credits: Succulent for the xloader image
Fattire for the idea that it might have formatted mmcblk0p1 (which it dead instead of mmc1)
You're welcome.
Might want to add that the cause of the "brick" appears to be that CM7 is confusing mmc1 and mmc0 and instead of wiping the first partition of the SD card, it's presumably wiping the first partition of the emmc, which contains the x-loader.
I already have said it.
Ah okay... well glad everything is fixed now.
fattire said:
You're welcome.
Might want to add that the cause of the "brick" appears to be that CM7 is confusing mmc1 and mmc0 and instead of wiping the first partition of the SD card, it's presumably wiping the first partition of the emmc, which contains the x-loader.
Click to expand...
Click to collapse
Bowing head in shame here...... Rookie mistake!
Looks like we have to make a bit of a tweak to the system then do some testing.
New download link due to a small scripting error.
Need help
Hi Indirect. I see that you have fixed your NT. I did not use sd i did install cm7 internally but i did format all the mounts . And now it just restarts in CWM. What should i do. Any idea please
Well guys, I'm still having problems. I ran the brick fix before you updated it - didn't work. I then re-ran after you updated it - still didn't work. It'll boot to CWM from SD, but won't boot to any ROM. Tried re-installing CM7 (didn't work), then I tried the Nook141root.zip which supposedly installs the BN 1.4.1 from CWM (also didn't work). Tried re-running the brick fix a handful of times after and before installing each ROM with no luck. Then I tried running it without installing a ROM. Tried the brick fix then I tried the BN 1.4.0 restore file. I tried on multiple freshly formatted SD cards and I even tried on a computer I was working on with a fresh install of Win7 with a fresh install of the drivers just to rule that out.
Before all this I had CWM and CM7 installed internally - if that makes a difference. Ideas?
Edit: More info. When trying to wipe data/factory reset in CWM I get the errror "E:format_volume: make_ext4fs failed on /dev/block/mmcblk1p2"...this occurs right after rebooting from the brick fix.
Edit 2: More info yet...in the brick fix I'm getting the text "error: device not found" twice right after entering "y" then again a handful of times later. Is there anything special I have to do in CWM to get it to detect it? I have sdcard mounted...
Im geting this and then my nt restarts by itself and then im back in cwm again so nothing is fixed.
Fatos said:
Im geting this and then my nt restarts by itself and then im back in cwm again so nothing is fixed.
Click to expand...
Click to collapse
What do you have mounted to get it the fix to detect the tablet? Does it matter?
scsione889 said:
What do you have mounted to get it the fix to detect the tablet? Does it matter?
Click to expand...
Click to collapse
Actually with mine it does not matter . I get till the step y or n without mounting nothing. Than i mount the sd card and press y and enter.
Than as u can see does try to write something and than my nook does reboot .
And the ending is the same. So no progress so far.
Fatos said:
Actually with mine it does not matter . I get till the step y or n without mounting nothing. Than i mount the sd card and press y and enter.
Than as u can see does try to write something and than my nook does reboot .
And the ending is the same. So no progress so far.
Click to expand...
Click to collapse
Were you running from internal or SD when it bricked?
Does it boot to CWM on it's own without an sd in the slot? If it does have you tried restoring/flashing a backup?
Reason I say about the backup is I just bricked my own systems on purpose when running from sdcard, it kept gpoing back to CWM after the xloader was returned to it. Restored an original backup and all is well again
CelticWebSolutions said:
Were you running from internal or SD when it bricked?
Does it boot to CWM on it's own without an sd in the slot? If it does have you tried restoring/flashing a backup?
Reason I say about the backup is I just bricked my own systems on purpose when running from sdcard, it kept gpoing back to CWM after the xloader was returned to it. Restored an original backup and all is well again
Click to expand...
Click to collapse
Yes i have had it internally.Not in an sd.
Yes mine doew boot to CWM on its own without and sd in slot. And yes i have tried restoring to re flash back up. Cause i have installed CM7 once and it did run well. But than after installing some programs became slow so i wanted to redo it again. And than i did format all: bootdata, cache, emmc, rom, system,sd-ext.
And then i installet cm7 again and all the installing went well againg . But it just want start cause is missing something in one of the mounts. So what i think is only needed if ill be able to restore the data that is in all those small partitions like emmc. I know that bootdata,and cached gets backed up but i dont know if the orthers are backed up or not.
Thanks for trying to help.
Edit: I have to go to university now. But if it would make it easier for you to help, I can shot a video afterwards with all the steps what i have done and how is my nook behaving now.Just let me know .
Edit1: I did try to restore to stock or update to 1.4.1 but it tells me MD5 mismatch.
Is it possible that i can push in with adb the files that are in the boot data, eMMc and other mounts i mean one by one.
I was running internal when it bricked. Only boots to cwm from SD now.
Sent from my Incredible 2 using XDA App
Fatos said:
Yes i have had it internally.Not in an sd.
Yes mine doew boot to CWM on its own without and sd in slot. And yes i have tried restoring to re flash back up. Cause i have installed CM7 once and it did run well. But than after installing some programs became slow so i wanted to redo it again. And than i did format all: bootdata, cache, emmc, rom, system,sd-ext.
And then i installet cm7 again and all the installing went well againg . But it just want start cause is missing something in one of the mounts. So what i think is only needed if ill be able to restore the data that is in all those small partitions like emmc. I know that bootdata,and cached gets backed up but i dont know if the orthers are backed up or not.
Thanks for trying to help.
Edit: I have to go to university now. But if it would make it easier for you to help, I can shot a video afterwards with all the steps what i have done and how is my nook behaving now.Just let me know .
Edit1: I did try to restore to stock or update to 1.4.1 but it tells me MD5 mismatch.
Is it possible that i can push in with adb the files that are in the boot data, eMMc and other mounts i mean one by one.
Click to expand...
Click to collapse
I'm in the same boat...I think when we did a format of the rom partition, we lost some data that was not backed up...That being said I have done a lot of reading and I think all hope is not lost.
We did not format the "factory" partition which from what I have been reading may contain a backup of the "rom" and other partitions.
I wonder if it is possible to pull the data from the factory partition, extract the data that we need and then push the appropriate files back to where they belong? It's way beyond my expertise, although I do have ADB working and I think if someone could point us in the right direction, it wouldn't be that difficult...I could be completely off base though...Good Luck and If I make any progress I'll make sure I pass the info along.
Need help!
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
ElectroMike said:
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
Click to expand...
Click to collapse
That's exactly what I've got. I'm going to spend a little time on fixing that up today. ADB just won't work through CWM for me.
ElectroMike said:
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
Click to expand...
Click to collapse
I had thought about a flashable zip. I will look shortly and build one
I tried repartitioning my nook and it really bricked it now. It won't boot from SD. Tried a different card and fresh download of CWM. I think it's totally borked.
Edit for clarification: repartitioned from within CWM on SD
Edit2: Tried a 3rd card (first 2 were 32gb, 3rd was 16gb) and it let me back into CWM. ADB still isn't working though.
Edit2 clarification: I only say ADB isn't working because the brick fix says device not found. If I'm wrong please feel free to correct me.
scsione889 said:
I tried repartitioning my nook and it really bricked it now. It won't boot from SD. Tried a different card and fresh download of CWM. I think it's totally borked.
Edit for clarification: repartitioned from within CWM on SD
Edit2: Tried a 3rd card (first 2 were 32gb, 3rd was 16gb) and it let me back into CWM. ADB still isn't working though.
Edit2 clarification: I only say ADB isn't working because the brick fix says device not found. If I'm wrong please feel free to correct me.
Click to expand...
Click to collapse
Mne does not say that but it restarts my nook. But it does not fix it. I think its just some small starting files missing. But im not so good so i cant help it. So im just sitting and watching around internet if there is any fix. It looks that they have had the same problem with NC to start with to.
[UPDATE #2]
I am now back on 1.4.2 stock (whew!!). Using the Ubuntu Recovery Unbrick sdcard did the trick. After doing that, I then flashed the raywaldo.com "repart.img" (which restores to 1.4.2). Thanks to all who offered advice. I've learned quite a bit about my NT during the past 24-28 hours. I'll hopefully get 10.2 successfully flashed tomorrow -- no more formatting! Only a safe wipe!! Cheers!
[UPDATE]
I now am able to boot from at least one SD card. I was able to put an sdcard image of 10.2 on a 4gb card and it DOES boot just fine. So it would appear that in worst case scenario, perhaps I can find a 16gb card that will boot and just use that (vs. internal memory). Does having a booting/working sdcard version of 10.2 give me any tools/etc. that might let me work on this internal memory (i.e. terminal emulator)?
I have a 16GB Nook Tablet that had been running a CM11 (KitKat) nightly. I was having WiFi issues (constant disconnects), so I decided to go back to 10.2 (or even 10.1.3). I did a stock reset to 1.4.2, and then flashed 10.1.3. It was acting flaky, so I thought "Oh, I didn't wipe everything before flashing, need to try this again". So during THIS "wiping" process, I was multi-tasking and went brain dead for a minute (I was on a conference call at work, IIRC). As I always do with my HTC phones, I went into "Mounts and Storage" in CWM and proceeded to format everything that shows up (yes, everything -- /rom, /bootdata, /factory, /system, /cache, /emmc, /data). When I put my full attention back to what I had just done, I had a VERY bad feeling..... (Trust me, I have already insulted my own intelligence enough over the past 24 hours -- so please, no posts telling me how stupid that move was...)
Anyway, here's where I am at this point:
CWM 6.0.2.5 Recovery is installed (internal). Any boot attempt just goes straight to CWM.
SDCard boots will not work unless I use the "plug the USB cable into computer first" trick (prior to this, sdcard boot worked fine). I tried the sdcard boot with the "repart.img" (which should supposedly fix partitions and get me back to stock 1.4.2), but I now get the RED "X" instead of the GREEN check, so that was a dead end. FWIW, I have used this method twice previously after other issues and it always worked perfectly.
This NT was purchased (sealed) as a part of a "lost freight" auction, so it can never be registered with B&N (which is fine with me). I only point that out as it relates to any "fix" process wiping out serial number, etc. -- in this case, that really doesn't matter to me. And considering I formatted /rom, it's probably already gone anyway.
(EDIT: I should have mentioned that I am also unable to use adb via USB cable with a computer. I've tried both a Win7 box and an XP box -- neither will ever install any drivers. It detects a new device, "NookTablet", then searches/fails to find driver, and then when I try to manually point it to driver in Device Manager, it says it can't find compatible driver. I'm using the standard usb drivers found here in several NT threads. I've used the NirSoft USB viewer and uninstalled the Nook-related entries several times and retried, but still no joy. )
So where do I go from here? Any attempt to flash anything using CWM doesn't really appear to do anything (well, it APPEARS to complete just fine, but when I reboot, it just goes back to CWM). Is the Ubuntu brick fix SDCard the best approach for me?
I basically just want to get some advice before I start trying things. I'm usually successful at self-fixing my messes, but this time I thought it might save me some headaches to ASK FIRST.
Thanks in advance!!
kltalley said:
...
I went into "Mounts and Storage" in CWM and proceeded to format everything that shows up (yes, everything -- /rom, /bootdata, /factory, /system, /cache, /emmc, /data). When I put my full attention back to what I had just done, I had a VERY bad feeling.....
...
Click to expand...
Click to collapse
In formatting /rom and /factory you wiped out the all factory-installed individual device data (serial no., MAC address, security encryption keys, etc.) which NT requires in order to operate (see http://forum.xda-developers.com/showthread.php?t=2575489 for more info).
Have you considered the unbrick methods described at http://forum.xda-developers.com/showthread.php?p=49638948? and http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/?
digixmax said:
Have you considered the unbrick methods described at http://forum.xda-developers.com/showthread.php?p=49638948? and http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/?
Click to expand...
Click to collapse
The sdcard "repart.img" I mentioned earlier was an attempt at the raywaldo.com unbrick. I immediately get the red "X" in the corner (vs. the green checkbox which indicates that it worked).
It would appear that the Ubuntu recovery/unbrick sdcard (that you linked to) might be my only viable option at this point.
Thanks, digixmax!
kltalley said:
The sdcard "repart.img" I mentioned earlier was an attempt at the raywaldo.com unbrick. I immediately get the red "X" in the corner (vs. the green checkbox which indicates that it worked).
It would appear that the Ubuntu recovery/unbrick sdcard (that you linked to) might be my only viable option at this point.
Thanks, digixmax!
Click to expand...
Click to collapse
Believe it or not, but I also did something just as bad as you did. Basically, I wiped out my Nook Tablet 16GB's entire partition table. However, I DID make dd dumps of all the important partitions such as /boot, /recovery, /factory, xloader, and /rom.
After rebooting the tablet, it obviously failed to boot, so I had to use a bootable CWM card. Plugged into my computer, adb shell, ran gdisk (GPT version of fdisk, because the NT uses GPT partition table), manually recreated partitions, then dd flashed the backed up partitions I made a long time ago (I always prepare for the worst in advance, just in case).
If you have a full backup, I believe you can recreate the /rom partition and extract the specific partition's contents into it.
Also, you should try installing a Linux distribution (I personally recommend Debian, but Fedora or OpenSUSE are also excellent. Ubuntu I do not recommend, funny as it sounds). Trust me, adb DOES work, even if you formatted everything. It's probably something with Windblows that is preventing you from accessing the NT's adb shell.
All is well again -- I have my NT back on 1.4.2 stock (see original post for details). Thanks to everyone!