So, I've no idea specifically where to start, so I'll just go from the beginning. Earlier today, I flashed a stock firmware for my device (I9300XXDLJ4 from the 'Stock Firmwares' thread) using Mobile Odin Pro successfully. No problems, except for when I forgot to factory reset the first time through.
More recently, I tried to re-flash CF-Root 6.4 to regain root, which didn't work as well as I had hoped, as I am now left with an unmountable /data partition on my internal SD, which means I cannot go any further in the 'factory reset -> restore' route. I have no idea what to do anymore - 30 Google searches later and about 20 separate flashes of firmware hasn't helped and I'm at the end of my tether. I really have no idea what other information to supply, so I guess if you guys have any idea you can let me know.
In addition, although a blank, yet working OS and phone would be better than a paperweight, I would like to keep my internal sd-card intact (or at least the partition with all my stuff on it). I also have a CWM6 back-up on my external sd if that could help me in any way.
So, yeah, whatever you can think would be greatly appreciated please and thank you.
(Long story short - unmountable /data partition on my internal sd means I can't boot/flash any 'proper' OS / it's soft bricked.)
UPDATE: Booted into stock Samsung firmware as above, not sure if it's because it's still got all the stuff from before and I haven't wiped it or it's genuinely fixed. May as well spend another half-hour on Odin to see what I can do.
UPDATE 2: Fixed. Mounting the /data partition only worked once I flashed the stock firmware - whether it's because of the recovery or the OS, I'm not entirely sure, but I'm now able to read/write to the /data partiton and I've just booted up my previous CM10 nightly, so... yeah. DO what you will with this thread mods. I'm done here, for now.
Irradium said:
So, I've no idea specifically where to start, so I'll just go from the beginning. Earlier today, I flashed a stock firmware for my device (I9300XXDLJ4 from the 'Stock Firmwares' thread) using Mobile Odin Pro successfully. No problems, except for when I forgot to factory reset the first time through.
More recently, I tried to re-flash CF-Root 6.4 to regain root, which didn't work as well as I had hoped, as I am now left with an unmountable /data partition on my internal SD, which means I cannot go any further in the 'factory reset -> restore' route. I have no idea what to do anymore - 30 Google searches later and about 20 separate flashes of firmware hasn't helped and I'm at the end of my tether. I really have no idea what other information to supply, so I guess if you guys have any idea you can let me know.
In addition, although a blank, yet working OS and phone would be better than a paperweight, I would like to keep my internal sd-card intact (or at least the partition with all my stuff on it). I also have a CWM6 back-up on my external sd if that could help me in any way.
So, yeah, whatever you can think would be greatly appreciated please and thank you.
(Long story short - unmountable /data partition on my internal sd means I can't boot/flash any 'proper' OS / it's soft bricked.)
UPDATE: Booted into stock Samsung firmware as above, not sure if it's because it's still got all the stuff from before and I haven't wiped it or it's genuinely fixed. May as well spend another half-hour on Odin to see what I can do.
UPDATE 2: Fixed. Mounting the /data partition only worked once I flashed the stock firmware - whether it's because of the recovery or the OS, I'm not entirely sure, but I'm now able to read/write to the /data partiton and I've just booted up my previous CM10 nightly, so... yeah. DO what you will with this thread mods. I'm done here, for now.
Click to expand...
Click to collapse
Good to read a thread with a quick "happy ending"!
Good work mate!
// Ohamn
Related
Hi all,
I searched long and hard for an answer to this one, but I can't make heads or tails of it. It started when I noticed that any apps I installed wouldn't stay through reboots, and any uninstalled apps came right back. So I tried reflashing Flashback 7.0 and 7.2, but the apps were still there. It does look like 7.2 installed correctly, although the apps were still there.
Then I tried flashing several different roms (TnT, Cyanogen, Vegantab, stock), but they wouldn't boot. Flashing back to Flashback allowed the tablet to boot, but the data was still there.
I tried manually formatting /data through cwm, but I got the lovely "Error formatting /data" message. Doing the normal cwm data wipe and repartition (4096,0 and 2048,0) didn't do anything either. I tried NVFlashing back to stock 4349, no good. I tried Flashback loaded with cwm 3.0.2.8 and the stock 1.2 recovery, but no avail. I blew away the partition table and nvflashed, no good. I tried pulling the battery, no good. I tried flashing the FORMAT utility, still stuck with this data. No matter what I do, it will only boot after installing Flashback 7, and then it retains the state it was in before going wonky.
The tablet works more-or-less for every app currently installed, apps load fine, all hardware appears to work fine, but once it's rebooted everything goes back to how it was when it went belly-up.
This has gotten the better of me, I'm hoping there's some nuance that you brilliant folk know of that I'm missing. Thank you for your time.
Both /data & /sdcard reside on the internal sd and are not touched by nvflash or by installing a new rom (all of which go on the internal nand (not sdcard). There are serveral ways to clear them. You can clear /data by doing a "factory/data reset" & repartitioning in CWM wll destroy/recreate both /data & /sdcard (so make sure you backup anything you want to save on /sdcard before you repartition). The standard repartition is 2048,0, but in some situations it is benefitial to repartition to 4096, 0 & then immediately repartition back to 2048,0.
After installing a new rom you should always do a factory/data reset, wipe cache & wipe dalvik to clear out data/installs from the prior rom.
Al
Thanks Al,
I forgot to mention, I've already repartitioned several different times, going up to 4096,0 then down to 2048,0 as I've seen recommended elsewhere. The wipe data/factory reset option also doesn't seem to be affecting the data staying put.
I remember a person with a similar situation. I believe rajeevvp had the person do some testng & it came out (in that case) to be a bad internal sd. He developed a way to use the external sdcard as the internal sd. I'll see if I can find the post or you can PM him.
Al
See this post http://forum.xda-developers.com/showthread.php?t=1156200 and specifically post #44 Guide to swap internal and external SD card assignments on the ViewSonic gTablet for users with partly-functional internal SD cards.
Al
Looks like the same issue all around. Thank a million, here's to hoping it works.
Get me a dmesg output first.
Second, since you're on the 1.2 bootloader branch, don't flash the custom CWM zip file which is only for bl 1.1. Just skip that step (step 1). The rest of the steps are bootloader-independent. Step 1. is only for letting you make backups and restores using the external SD card instead of the internal one.
Third, I'd like to see the results of the test commands given in the thread that aabbondanza posted above.
Finally, for CWM 3.x and higher, I have another (and easier) technique that I think will work for backups and restores, but, I never tested as I didn't want to change bootloaders. Let me know if you're willing to be a guinea pig for testing this.
rajeevvp, the result of the test directory/file creation on /data and /sdcard were similar to the other poster, with the directories and files not being retained after unmount or reboot.
The results of the test commands are attached. Thanks again for all your help. Additionally, of course I'm willing to be a guinea pig for anything you've got in mind.
sktsswth said:
rajeevvp, the result of the test directory/file creation on /data and /sdcard were similar to the other poster, with the directories and files not being retained after unmount or reboot.
Click to expand...
Click to collapse
From the dmesg1.txt file I see that you have the non-standard internal SD card make that seems to cause this sort of problem:
<6>[ 10.001007] mmc2: new high speed SDHC card at address aaaa
<6>[ 10.007139] mmcblk3: mmc2:aaaa SE16G 14.8 GiB
<6>[ 10.011722] mmcblk3: p1 p2
Click to expand...
Click to collapse
You can either return the tablet to VS or try my workaround hack along with a new CWM for 1.2-based bootloaders (soon).
Either way, I'd like to continue this discussion further in this thread.
rajeevvp said:
From the dmesg1.txt file I see that you have the non-standard internal SD card make that seems to cause this sort of problem:
You can either return the tablet to VS or try my workaround hack along with a new CWM for 1.2-based bootloaders (soon).
Either way, I'd like to continue this discussion further in this thread.
Click to expand...
Click to collapse
Since some of these tablets are showing up with different internal sd cards than most of us, is it possible that when we are having these people nvflash back to stock, that the bct's config of these new chips would be different & we are causing the problem by flashing the incorrect bct back to the device? Would it be safer to modify our nvflashes to read & use the user's bct when nvflashing back to stock?
:crying: well, as you may read I had bricked my nook tablet of 16 GB, i was installing cm 10 , it worked fine but I forgot to do the factor reset to delete Google apps, so I had my nook tablet with CM 10 and then upgraded the screen so it could have 10 sensitive points, but it would not open youtube or the market, after realizing this i tried to install gapps WITHOUT deleting the ones already installed, (i know stupid) so now the tablet would not launch cm 10, it would stay stuck on the start-up with the blue circle of cm. Then i would only go into CWM and i managed to install and run cm9 but i could not use the touch screen, I thought it was because of the screen upgrade, stupidly i formatted partitions and wipe data and cache and messed with things i shouldn't thinking i could make it work, so yeah after that i could only get to cwm without the ability to install anything becase either 1) it wouldnt work, 2)it would say something about ext4 or fat32, or 3) It would say it could not open the package because it was corrupted. Tired of all this i sured into the web and tried some things that didn't work , i tried these :
http://forum.xda-developers.com/showthread.php?t=1657159
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
And some others that i tried but i dont remember them, but the most important was this one : http://forum.xda-developers.com/showthread.php?t=1605664 , it said it could repair ANY Brick but it just made my semi-bricked nook into a Total death Nook brick, (I'm not saying anyone is responsable for this im just saying)
I tried this many times with a sandisk 2gb and pretty much sure i had tried all how to less the ones that use a sdcard of more than 2 gb because i dont have.. anyone knows how to fix this?? i cant use a bootable CM, already tried and didnt worked,
PD: I think my partitions are messed up too because when i am in cwm from a bootable sd , my serial number is "00000000000" , and i dont have a backup... My Nook has been brike for almost a month , And sorry if i said something with no sense, i had not fully learned the language, i speak it very well but this is kindda harder :crying:
djjean19 said:
:crying: well, as you may read I had bricked my nook tablet of 16 GB, i was installing cm 10 , it worked fine but I forgot to do the factor reset to delete Google apps, so I had my nook tablet with CM 10 and then upgraded the screen so it could have 10 sensitive points, but it would not open youtube or the market, after realizing this i tried to install gapps WITHOUT deleting the ones already installed, (i know stupid) so now the tablet would not launch cm 10, it would stay stuck on the start-up with the blue circle of cm. Then i would only go into CWM and i managed to install and run cm9 but i could not use the touch screen, I thought it was because of the screen upgrade, stupidly i formatted partitions and wipe data and cache and messed with things i shouldn't thinking i could make it work, so yeah after that i could only get to cwm without the ability to install anything becase either 1) it wouldnt work, 2)it would say something about ext4 or fat32, or 3) It would say it could not open the package because it was corrupted. Tired of all this i sured into the web and tried some things that didn't work , i tried these :
http://forum.xda-developers.com/showthread.php?t=1657159
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
And some others that i tried but i dont remember them, but the most important was this one : http://forum.xda-developers.com/showthread.php?t=1605664 , it said it could repair ANY Brick but it just made my semi-bricked nook into a Total death Nook brick, (I'm not saying anyone is responsable for this im just saying)
I tried this many times with a sandisk 2gb and pretty much sure i had tried all how to less the ones that use a sdcard of more than 2 gb because i dont have.. anyone knows how to fix this?? i cant use a bootable CM, already tried and didnt worked,
PD: I think my partitions are messed up too because when i am in cwm from a bootable sd , my serial number is "00000000000" , and i dont have a backup... My Nook has been brike for almost a month , And sorry if i said something with no sense, i had not fully learned the language, i speak it very well but this is kindda harder :crying:
Click to expand...
Click to collapse
Well if you can load into cwm I would factory reset/wipe data, clear cache, clear dalvik cache. Trying flashing CM10. If you can't internally use the SDC version. Boot up CM and go to firmware flasher to change your touch back to stock. If you cannot do this I have various methods of "unbricking" collected from different sources. Its in this thread so Adam Outler Reflash method may be the path you have to take.
I tried the first method but in data/wipe factory reset it tells me : ''E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2'' but then it said ''data wipe complete'', reflashed cm10 and rebooted but it just shutted down the device it didn't rebooted, so im trying next method
djjean19 said:
I tried the first method but in data/wipe factory reset it tells me : ''E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2'' but then it said ''data wipe complete'', reflashed cm10 and rebooted but it just shutted down the device it didn't rebooted, so im trying next method
Click to expand...
Click to collapse
I may be wrong but mmcblk1p2 is a ext4 partition on the internal storage. Don't know what it does at all though. Continue with the different methods and see what works.
datallboy said:
I may be wrong but mmcblk1p2 is a ext4 partition on the internal storage. Don't know what it does at all though. Continue with the different methods and see what works.
Click to expand...
Click to collapse
mmcblk1 is the external sdcard.
datallboy said:
I may be wrong but mmcblk1p2 is a ext4 partition on the internal storage. Don't know what it does at all though. Continue with the different methods and see what works.
Click to expand...
Click to collapse
I tried most of the methods (except adam outlers method and R3 method given that my biggest sdcard is a 2gb sdcard) they didnt work, however , i mánaged to run cm 10 on a sdcard , but i cant find the firmware flasher to return the touchscreen to stock... I like this of running a OS from a sdcard though and i would use it , but cm10 is too unstable , so i will turn touchscreen back to stock to run cm7 which i think es more stable
Hi there, try this out http://forum.xda-developers.com/showthread.php?t=2179403
The second file will be about 510 mb.
I also formatted some partitions... bad idea. I tried Ray Waldo's method but it didn't work. Perhaps this one will work for you?
djjean19 said:
I tried most of the methods (except adam outlers method and R3 method given that my biggest sdcard is a 2gb sdcard) they didnt work, however , i mánaged to run cm 10 on a sdcard , but i cant find the firmware flasher to return the touchscreen to stock... I like this of running a OS from a sdcard though and i would use it , but cm10 is too unstable , so i will turn touchscreen back to stock to run cm7 which i think es more stable
Click to expand...
Click to collapse
The firmware flasher is one of the apps that comes with CM10.
SomeDoofusLover said:
Hi there, try this out http://forum.xda-developers.com/showthread.php?t=2179403
The second file will be about 510 mb.
I also formatted some partitions... bad idea. I tried Ray Waldo's method but it didn't work. Perhaps this one will work for you?
Click to expand...
Click to collapse
I was about to try this, but accidentally booting into cm i booted into internal boot instead of sdc boot, for my surprise it was loading cm 10 :laugh: , and way more stable than the sd card, so i went to the storage and i got 4 Gb of storage for apps, weird given that my Nook has 16Gb but still happy, it run smoothly, ad i will stick to it, i figure out that maybe my boot partition is damaged so I need the sd boot to go to the internal boot, , I'm making a thread of this , this may help someone else with a dead nook :good:
@datallboy : I figured that out somewhat late, it comes with cm 10 from version 11/14 or so , i was using version 11/08 because i didn't knew there was a new one, now i'm running version 12/31 Internally and it is stable , thanks , i wouldn't figured this out without your help
First off, I am no expert so please be gentle! I previously rooted my old Samsung Galaxy S i9000 and installed ICS, which went OK, but the phone became quite slow and unstable. I was advised to install RemICS and downloaded all the zip files from this forum, and put them on the external SD card. I followed the developer's instructions to the letter, as well as reading everything I could find on the subject. The reset and data wiping went fine, but the installation of the ROM didn't. It halted with an error message -`ROM incompatible, trying to use an invalid partition'. I repeat that this is supposed to be the specific ROM for the i9000. The phone now won't boot into recovery. It stops with an orange Android logo and the text `Powered by Mackay Kernel'. It won't boot into download mode either. The Mackay screen stays there however long I leave it. I really need help from the ROM developer but I can't post to that forum. How can I either boot into recovery or into download mode? Is this ROM reliable? What could I have done wrong?
More info:
Presumably everyone is on holiday! But just in case anyone is reading, there is further news. The reason I could not start recovery mode was that the button sequence was different from what I had been told. It now boots reliably into Mackay (which of course is TWRP). I have found that the phone is unable to mount the partitions DATA and SYSTEM - they seem to be corrupted. Hence it has not wiped DATA, although TWRP wrongly reports success. I have tried updating the partitions to ext3 or ext4 but this fails every time. I could format the thing from Windows but that will wipe everything including recovery of course. I need a tool to repair these partitions, but have not found anything so far. This may well have been the reason the phone was getting creaky in the first place.
I have copied a new ROM to the external SD card, using a card reader, and inserted this into the phone. Strangely the TWRP file manager reports that EXTERNAL SD is a sub-folder of SD CARD, and that is empty. The file manager does not show the real external SD card. But the real external SD shows up on the Windows USB connection. What is going on?
When I try to mount the partitions, DATA and SYSTEM can't be checked - the other partitions (Cache, sdcard, and emmc are all checked).
kingGrn Copeland
Well for the benefit of anyone else with the same problem, I have managed to re-flash the ROM back to stock. It just took 3 days of intensive web browsing until I understood how to do it, and found software that worked - a lot of stuff out there has errors.
To summarise, the problem was:
1. Data and System partitions became damaged, so phone became unstable.
2. Attempt to upgrade ROM failed because of damaged partitions.
3. Could not boot phone into recovery or download because button combination was different from what I was told.
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Yes, someone did tell me that, and I would have done that straight away if I could have gotten into download mode. We live and learn
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Click to expand...
Click to collapse
Thanks this wa useful for me too.
I am having an issue creating backups. Last time I had issues with what seemed like the sd card, I bought a new 64 gig card and replaced my old one.
The old one still works fine with an adapter into my pc, but I wrote it off and sucked it up.
I just tried again making a backup in TWRP with an error, "unable to create backup folder". So, I switched over to CWM and tried the backup. Same issue.
I just checked with my phone plugged into my pc and the file system is defined as "Generic Hierarchal" which I've never seen before. I am almost positive I formatted it initially as either fat or ex fat. With the phone on, I have no issues with the card. I have music and other data on it and it reads just fine.
Other possibly relevant history:
previous rom was Beans 21 and was unable to update to 22 (do not remember the error)
wiped and loaded Alliance's latest V8 with no issues. Been running Alliance for a few weeks now with zero issues. (other than backup)
Do I need to wipe my card and format it in the phone? I think previously I formatted it in my win 7 pc with an adapter.
TIA for any info
Formatting the card with TWRP is probably better
I had this issue with an S3 and nothing would work. I tried mounting/remounting, formatting, and even a new SD card. It finally worked with a new SD, which is really weird because it was an old SD card compared to one of the newer ones.
Thanks for the response. I have 2 cards. Just cleaned off one and formatted in the phone. Still fails trying to do a backup. I hate the thought of buying a third 64 gig card.
I think I'll try going back to stock and see what happens. It'll be a while before I can. Sucks I can't backup first.
Thanks again for the response
interesting update, for anyone that might be watching this post: I d'loaded skips updated toolkit from here: http://forum.xda-developers.com/showthread.php?t=2052788&page=10
and was able to make a backup.
just FYI
Bought a Sammy 64 and same issue. Unless anyone has any other suggestions, I'm going to Odin back to stock, I guess.
back to stock, unlock, root fixed it. just fyi.
georgepink said:
back to stock, unlock, root fixed it. just fyi.
Click to expand...
Click to collapse
Not. Tried to load another rom and can't read from ad card. Damnit. Any help would be appreciated.
more drama...I re-loaded twrp, b/c I found an old post with roughly the same issue. It said to use cwm to fix permissions. Well, cwm doesn't offer that anymore, the comment is that it was placebo effect. twrp still does offer it. I ran it and then rebooted to android, then rebooted into twrp reco again and was able to load Alliance v8 again.
so, until 4.4 roms appear (which I will have to go back to cwm for, unless twrp gets updated) I guess I'm set.
I'd still LOVE to hear from someone who might know how this happened or what exactly happened, to know what to avoid.
Thanks again, to the one person that responded.
Back to square 1, cannot make nandroid backups.
In CWM v6.0.4.3 here's the errors:
trying to backup: Can't mount Backup Path
trying to mount external_sd: Error Mounting /external_sd
In TWRP v2.6.3.0 here's the errors:
trying to backup: backup folder: /external_sdcard/TWRP/Backups/
E:unable to create folder: /exterenal_sdcard/TWRP
E:Failed to make backup folder
Any thoughts? I know I've posted this multiple times, but not sure where to turn. I suspect if I go back to unrooted stock again and unlock / re-root, load twrp and fix permissions, it will work again for a while. But not permanently. I really want to fix this once and for all. But am not getting any clear direction to go. I have searched on and off XDA to no avail. hoping this time is the key. Thanks for reading and potentially helping.
[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!