Related
So my phone got stuck at boot screen. Bell says I get full replacement, but I'm gonna lose all the data. I have the internal full of children opening gifts on Christmas.
Reading a million forums. Tried to learn enough to flash the firmware with odin. Tried flashing the stock JH2 back to phone. Phone boots to recovery and says problem mounting SD.
Can ADB be used to connect to phone in "Download mode" to Pull the media???
PLEASE PLEASE help?????
after odin is done the phone reboots to:
E:Can't mount /dev/block/mmcblk0p1
(no such file or derectory)
E:copy_dbdata_media: Can't mount SDCARD:\copy default media content failed
I'm still desperately trying to get my files. I've read about 1254 more threads. Found this one about flashing back to eclair...
http://forum.xda-developers.com/showthread.php?t=797302
So far I tried JH2, JL2, JM8 and still no luck. Anybody out there got any ideas?? links to help or compassionate remarks?
Phone no boot need remove files inside...is this really an impossibility??
Argh.... it never happens when the internal has useless data aye.
You tried flashing a firmware using all three files (PDA, modem, CSC) with repartition?
P.s. apologies if you have tried all this, just trying to establish a baseline
Sent from my GT-I9000 using XDA App
From what i understand the internal SD card has 2 main partitions. One that's about 2 gigs for Android OS and apps and the remainder of the card stores media and such. (I think that's correct) So I've tried carefully to just poke around the OS area of the SD card in hopes that I can get it to boot up just once to connect and get the pictures off it. I'm fairly sure that "re-partition" would erase the whole card.
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Hoodmin said:
From what i understand the internal SD card has 2 main partitions. One that's about 2 gigs for Android OS and apps and the remainder of the card stores media and such. (I think that's correct) So I've tried carefully to just poke around the OS area of the SD card in hopes that I can get it to boot up just once to connect and get the pictures off it. I'm fairly sure that "re-partition" would erase the whole card.
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Click to expand...
Click to collapse
Repartition only erases the 2GB portion, ive done several repartitions and it never touched my personal files on the internal SD
Hoodmin said:
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Click to expand...
Click to collapse
That won't work...the 'internal SD' is not a SD card in the traditional sense (standard, mini, micro) - it's a physical chip (IC) that's soldered on to the mainboard.
I haven't heard of anyone being able to pull data off a phone that's got the mmcblk0p1 failure. The best I've heard is of people repartitioning/formating the sd memory in order to get it working again - but of course, that would mean losing all data...sorry...
As what EarlZ said, repartition won't touch the part of the SD dedicated to user data. I've flashed via Odin countless of times and never once did my internal SD get wiped with a repartition so why not flash to something like JPU with repartition using 512 pit file?.
Edit: and reading the error seems to tell me it's a problem in the 2GB portion of the internal SD where the system and such get stored. So yes, do try a repartition. I guarantee you that your user data will be safe. The only time it would get wiped is if you actually choose to format that partition like how one does in Windows or through the settings. Odin flash won't do this most definitely.
If that fails...
Also take a look at this...
This guy seemed to have been lucky and got is supposed dead I9000m SGS working again. Here's his procedure:
http://forum.xda-developers.com/showthread.php?t=905975
Worth a shot.
Well hot damn them are some good replies. I was brave enough to try re-partition and a few mod roms like in the thread mention as well as a few thread techniques I read. I must have read about 4622 threads by now. Still no luck for me I really really appreciate the help.
Thinkin I might just go wrap up the kids christmas presents tonight while they sleep and just make em open them all again hahaha.
In the mean time I'll just keep readin and keep tryin. Learned a lot at least.
So....
Original problem = boot cycle
-I flash back to JH2 and at least to phone gets to recovery mode and i see the mmcblk0p1 error. progress
-try flashing to the newer JL2 and it goes back to boot cycle
-try flashing back to JH2 to get recover mode again and still boot cycle
-read a million forums about trying mod roms and other techniques and still boot cycle
-get encouraged that re-partition will only affect OS side of SD card and try a million things again. Still boot cycle
-decide to go back to the JK4 that i started on and seems to be the root of all evil and then BAM recovery mode returns and this time it even recognized the device
-any attempt to connect with device either with kies or windows explorer causes PC crash
-phone even recognized by ADB I "think" this program could be used to try and "pull" media from the device but that's just a guess and I don't know how to use it
-the error now is not mmcblk0p1 instead: E:Can't/b mount /devlock/stl10 which could mean something or could be just the same and it leads me to this thread: http://forum.xda-developers.com/showthread.php?t=788850
-try flash techniques in the thread and back to boot cycle
-try going back to the JK4 so I have recovery mode again and still boot cycle. progress gone
I'm gonna flash this damn thing again and again until the damn copper lights on fire
Wow i Admire you man.Listen i dont know much about ADB but i think i saw a post of someone that literally pushed files in his internal card with it,and i clearly remember him saying he could browse through his phone although its card was burned.If so then a single copy would be possible.Since i cant help more,you better start reading on how to use it and find basic commands for it.
I wish you the best man!!!!
Have you tried this kernel: http://forum.xda-developers.com/showthread.php?t=901772
I seem to be able to get that running on my dead GT-i9000M. It has a file browser so maybe you can see if your pictures are even there/accessible. Also has a USB Mass Storage option but it didn't seem to work for me.
However, phone is still dead and needs to go in for repairs/replacement.
OK so now I'm f&*#ed
Tried JP1 method from this stupid page
http://briefmobile.com/how-to-android-2-2-on-galaxy-s
and now I don't have download mode anymore.
somebody plz just shoot me
EDIT: Ok excuse this panic post. I still had connection to ADB and a simple "adb reboot download" command got me back.
Wow thank JDROM. This recovery mode really looks promising. I got the file manager working but I can't seem to find any directories with DCIM/ label or any media. Sure looks like this could help me somehow. Might only have half the SD mounted or something. I'll have to play around and read some more, but I gotta say this is the best progress I made in a while.
THanks SO much
Edit: Found in File manager to run partition manager and formating options show up. In here there is mounting options to /mnt/sdcard or /mnt/external_sd except when I try it returns the E:Can't mount /dev/block/mmcblk0p1 to /mnt/sdcard with parameters vfat(null) So hmmmm....
Edit: Also learned a bit more about ADB commands to possibly ""Adb pull /sdcard/DCIM"" if I ever get it mounted.
Well that's it for me. The quest is over. I admit defeat. Memories Lost. Game Over
That sucks man...i had a bunch of stuff on my phone that i lost when the internal died....mine took out the external sdcard i had in it too - so all my backups were destroyed as well!
Moral of story: Save important crap on something like dropbox!
Some dev should make a program that automatically syncs certain directories (like pictures, or backup folders) to dropbox. I'd donate for that.....
I have screwed up my nook. Need some input. I was running nookie froyo on the internal mmc when I wanted to try out the honeycomb rom, but it seemed to hang half way through, so I rebooted the device. But it wouldntnt turn on. Now the nook color will not boot up unless I have an image on the micro sd. I think I may have corrrupted my internal flash. How do I fix it?
I have tried booting up clockwork and repartitioning data and system and reinstalling stock but still wont start without the micro sd.
Any suggestions?
You need to reimage your boot partition. There are several threads on this in the general forum. Including one asked by me where someone linked to several threads and I replied with the exact thread I used to get the boot.img.
A more to the point response:
Go here:
http://forum.xda-developers.com/showthread.php?t=931720
Cheers
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?
This always confuses and creates a lot of anguish and anger and rage.. i've had to redo the plaster on the apartment walls seven times and replace 4 LCD screens from my violent outbursts as a result of this.
This it it:
EMMC and SD.
EMMC, sure, easy, simple - install, get rom manager, use TWRP as a tool for flashing and updating roms.
SD, single and dual-bootable, not so easy. Error messages. Update failures. Screams, tears, coffee-shop outbursts resulting in numerous police calls and once to a mental ward facility.
Question:
How do I manage between the two. I eff up the EMMC trying to update the SD, and so on. They don't make it easy, unless I'm just for some reason blindsided by this.
Rundown:
TWRP 2.2 with its touchscreen feature, love it. Cool, stylish, features, yeah. Easy got that on my EMMC.
So question question, is there anyway to get TWRP installed on my SD, or any type of usable interface that doesn't muck up and just flash something if it has update-*.zip in it standalone without gui functionality. It's annoying, and I've had numerous problems with it breaking down and having to reinstall everything or go deep into it and fix a broken sector to get it working.
There has to be a fix for this, no?
Myself (and those around me as a result of this) would greatly appreciate any input.
Thanks
echoedge said:
This always confuses and creates a lot of anguish and anger and rage.. i've had to redo the plaster on the apartment walls seven times and replace 4 LCD screens from my violent outbursts as a result of this.
This it it:
EMMC and SD.
EMMC, sure, easy, simple - install, get rom manager, use TWRP as a tool for flashing and updating roms.
SD, single and dual-bootable, not so easy. Error messages. Update failures. Screams, tears, coffee-shop outbursts resulting in numerous police calls and once to a mental ward facility.
Question:
How do I manage between the two. I eff up the EMMC trying to update the SD, and so on. They don't make it easy, unless I'm just for some reason blindsided by this.
Rundown:
TWRP 2.2 with its touchscreen feature, love it. Cool, stylish, features, yeah. Easy got that on my EMMC.
So question question, is there anyway to get TWRP installed on my SD, or any type of usable interface that doesn't muck up and just flash something if it has update-*.zip in it standalone without gui functionality. It's annoying, and I've had numerous problems with it breaking down and having to reinstall everything or go deep into it and fix a broken sector to get it working.
There has to be a fix for this, no?
Myself (and those around me as a result of this) would greatly appreciate any input.
Thanks
Click to expand...
Click to collapse
I'm not really sure what you are asking. No kind of recovery program (either CWM or TWRP) can flash roms to the verygreen SD setup (what you called single boot). They have to be installed using the copy to boot partition method. And on Racks' dual boot SD you have to use his specially modified version of CWM to flash roms there. And the roms to be flashed there have to be specially modified before flashing too.
If you try to flash any unmodified rom zip with either TWRP or CWM it will always get put on emmc. That's what the roms are hard coded to do. It makes no difference whether the recovery is on emmc or SD, it will always install the rom to emmc.
Also remember, even if you somehow get TWRP installed on your SD, whatever you tell it to do, it does it to emmc. If you say wipe system, it wipes emmc system, not SD system, and same with other functions in TWRP. The same is true using an unmodified version of CWM.
I have heard that eyeballer may be working on a modified version of TWRP that may do things to SD, but I don't think he has released it.
Look on my tips thread linked in my signature for an explanation for the difference between flashing to emmc and installing on SD. There is also an explanation of the difference between the two types of SD installations.