Database Develop

CWR does nothing

My nook color recently got stuck on the boot screen for CM7 where the blue android text just chills out in the left corner. This happened right after my nook ran out of battery power.
I have gotten it to boot all the way into CM7 occasionally. However, it is not reliable at all, so I've tried to restore it to stock and reflash the whole thing.
I tried to do this by booting into recovery and then flashing the restore to 1.01 stock zip file, but when the nook rebooted it was still stuck on the android text. I have tried flashing everything related to restoring nooks, but to no avail.
I thought that maybe my CWR was broken, so I tried making a CWR sd card but even when I flashed the restore zip, my nook's boot still gets stuck on the android text.
What do you think I should try to do now?

You are able to boot into cwr though? If so have you tried downloading the stock image file again? Could be the file is corrupt.

I just downloaded it again and it still doesn't work.
I don't think that the problem is the zip files. I think that CWR is the problem since I've tried formatting /system and /data and tried repartitioning boot, but nothing happens...

I just tried to restore my nook to stock through ADB, but it still tried to boot into CM7. I guess that rules out CWR as the problem...
I also made an ext4 compatible CWR SD and tried the restore 1.01 zip again. This time I got past the android text and instead got to the grey android text from the rooted nook boot. However, it just sat there, stuck in a loop.

Odd, that even after wiping system and data that you'd have anything to boot into. You aren't leaving a bootable sd card in place are you?

I make sure to take out the SD card before rebooting.
Is it possible to check to see if CWR/ADB is actually writing to the correct partitions?
EDIT: I do not think that my nook is keeping any changes that I make to it...
I managed to boot into CM7 and I uninstalled a few apps and changed the max clock to 800mhz. Then I rebooted and eventually got back into CM7 and my apps magically came back and my max clock was reset to 1.1ghz.

okay that is very odd. Unfortunately I've never run into this or even read about it before. Hopefully someone here will be able to give you a tip that will help you fix this.

I've been having same issue for a week now. I tried everything I was able to find here but nothing is wokring. It seems like my nook became a read-only device. No matter what I do it goes back to previous stage.
I was running CM7 RC4 and system hung so I rebooted and that was it. It displays "Android_" on the bottm for about 10-15 sec and reboot.
I tried
CWR 3.0.0.5
- Repratition to stock nook.
- Getting error when I try to format system and data - I thought it was because CM7 was setting system to ext4.
- ADB and DD boot.img, System.img and copy Factory to mmcblk0p3
- Try to restore from back up I made
- Nothing works but goes back to boot loop
CWR 3.0.0.6 - One I got from CM7 install to emmc thread
- System format works
- Install latest nightly
- Restore from back up
- ADB can't find device - This is odd and couldn't find a way to fix it yet.
- Tried to install Stock zip but going back to CM7 boot loop
CWR 3.0.1.0
- Can't format data/system
- ADB to delete partitions and create them again but it doesn't help
- Tried all zip files to bring it back to stock - no go
- ADB to copy Factory.zip to emmc partition - umount and mount again then file I copied is gone.
- Deleted partitions and reboot but some how I got back to CM7 loop
I see people start to talking about CM7 boot loop issue. I saw this thread and man this is same issue I'm having! Let me know if you some how resolved this issue. I will do the same if I can find one.

Naw, I haven't resolved it yet...
I will post the solution if I do though!
Perhaps it's just a coincidence, but I am also stuck running RC4. Maybe there's some weird glitch in RC4 that makes the file system read only or something...?

I went from RC4 to stable with no problem. I did notice that CWR was not mounting the system and data partitions so I did have to do that when updating. Not sure why they aren't mounting automatically.

From the Dummies guide link....Here...
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.
I had to use that last file after my hard crash. Seems that te /boot gets corrupted and tis seemed to fix it for me. After this you will probably need to do a full wipe and reinstall.
My order was...
rebuild /boot
reflash to stock
reflash to CM7
not sure why this worked...just did.
edit: just noticed my H key isn't always working...makes me type like a alf drunk brit..

deadbot1 said:
From the Dummies guide link....Here...
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.
I had to use that last file after my hard crash. Seems that te /boot gets corrupted and tis seemed to fix it for me. After this you will probably need to do a full wipe and reinstall.
My order was...
rebuild /boot
reflash to stock
reflash to CM7
not sure why this worked...just did.
edit: just noticed my H key isn't always working...makes me type like a alf drunk brit..
Click to expand...
Click to collapse
I tried this too but mine didn't come back.

Hmm. dunno. Maybe you can get samuelhalff to chime in...he was helping another guy out with something similar. searc in the threads for his name and your problem...wasn't to long ago.
edit---http://forum.xda-developers.com/showthread.php?t=1022941 this was the thread I was talking about...doesn't appear they came up with a solution.

I tried all the things you suggested guys, but nothing worked...
Although I think I made some kind of progress... I tried to dd stock boot.img and system.img files onto my nook and now CM7 just bootloops instead of hangs!
Hopefully we can get this sorted out soon, or else I may try what one member suggested about microwaving it so that you can get a new one...

Odin failure or hardware failure?

My Cappy is having some serious issues! It used to run slimROM 4.2 and untill the night that it started illuminating the ceiling of my room with the ATT bootloader logo. I woke up checked it out and... nothing would run. System kept rebooting without end. As I am a somewhat knowledgeable flasher got into recovery mode and flashed my rom again. It went to the ATT bootloaders then it showed the slimROM logo as if it were to load it and then the screen went off. Dead!
I tried Heimdall SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click without any success.
Last, I tried returning it to stock using ODIN and this is the error message that I get
--Copying media files...
E:failed to mount /sdcard (no such file or directory
E:copy_dbdata_media:Can't mount /sdcard your storage not prepared yet. Please use UI menu for format and reboot actions.
Media files copy failed.
--Wiping data...
Formatting /data...
E: format_volume: rfs format failed on dev/block/mmcblk0p2
Formatting /dbdata...
Formating /cache...
Data wipe failed.
-- Applying Multi-CSC...
Installing Multi-CSC
Applied the CSC-Code 'ATT'.
Successfully applied multi-CSC
Click to expand...
Click to collapse
.
That's it. I think my /sdcard is dead. Are there any other possibilities and maybe a chance to bring my phone back to life? Please help!!!
I will be generous to anyone who can help.
Best

frenzisor said:
My Cappy is having some serious issues! It used to run slimROM 4.2 and untill the night that it started illuminating the ceiling of my room with the ATT bootloader logo. I woke up checked it out and... nothing would run. System kept rebooting without end. As I am a somewhat knowledgeable flasher got into recovery mode and flashed my rom again. It went to the ATT bootloaders then it showed the slimROM logo as if it were to load it and then the screen went off. Dead!
I tried Heimdall SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click without any success.
Last, I tried returning it to stock using ODIN and this is the error message that I get
.
That's it. I think my /sdcard is dead. Are there any other possibilities and maybe a chance to bring my phone back to life? Please help!!!
I will be generous to anyone who can help.
Best
Click to expand...
Click to collapse
When you tried Heimdall, did you use a different USB port?
Also, is that quote from Odin/Heimdall? If so, you might wanna try other GB versions (Heimdall UCKF1 worked for me before when Odin KK4 didn't).
Another thing, do you have a external sd? If so, try booting with it in.

Booting of External SD card
BWolf56 said:
When you tried Heimdall, did you use a different USB port?
Also, is that quote from Odin/Heimdall? If so, you might wanna try other GB versions (Heimdall UCKF1 worked for me before when Odin KK4 didn't).
Another thing, do you have a external sd? If so, try booting with it in.
Click to expand...
Click to collapse
I the quote is from Odin. What is extremely weird is that right after i posted this. My phone booted into GB. I then proceeded to see what my storage was doing and it turns out that I am somehow (I am not sure how this happened) i am running of my External SD card. My phone still can't see any internal SD card. Any suggestions?
Should i try to use ROM manager and flash recovery and try a ROM from there?
I am still worried that my Internal SD is not working.

frenzisor said:
I the quote is from Odin. What is extremely weird is that right after i posted this. My phone booted into GB. I then proceeded to see what my storage was doing and it turns out that I am somehow (I am not sure how this happened) i am running of my External SD card. My phone still can't see any internal SD card. Any suggestions?
Should i try to use ROM manager and flash recovery and try a ROM from there?
I am still worried that my Internal SD is not working.
Click to expand...
Click to collapse
***First of all, don't touch ROM Manager, it doesn't do well with the Captivate.
Custom recovery is flashed through kernels with Odin 1.18 (or 1.17). You simply grab the .tar file and put it in the PDA slot while you phone is in download mode. (On stock GB, you'll want Corn kernel)
Now my guess is that your external sd needs reformat. Backup w/e is on it (same with your internal if you can access it from your pc) and full format it to FAT32. If that alone doesn't fix it, wipe your internal as well.

[Q] Is my internal storage dead?

I am trying to get my Son's Captivate back up and running.. while it has no phone service, he uses it all day long. It was running Cyanogen Mod 10 .. he sat it down to eat.. when he came back the screen was black with the buttons lit up and no response.
He did a battery pull to restart it and it came back looping Error to mount /SDcard and a count down.
I got it into recovery and am not able to mount /data or /emmc. And it is failing to install a ROM from zip.
I tried using "I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click" and it runs through the process.. flashing Kernal, Modem, FactoryFS, DBDataFS and CACHE successfully.. then the device reboots and goes through a few things on screen, and fails on Formatting /data ( E:format_volume: rfs format failed on /dev/block/mmcblk0p2 ) but everything else says success. Hitting "reboot system now" says that it cant copy the log because of failure to mount /emmc.. then reboots to the same recovery and does the copy of Media and Appling Multi-CSC (their spelling mistake not mine) over again.
Flashing back to a CWM 6 recovery and still no mounting of /data or /emmc. And it just boots right into the recovery.
I tried --repartition with Heimdall and it said it uploaded the S1JE4.pit fine. Same things..
So is there anything I can to to test the internal storage to KNOW if it is faulty or is there anything else I can do?
I would really like to get this thing working again for my little dude.. he is so sad as all heck to not have his Android Buddy. :crying:

Seems likely internal sd may be dead, particularly if someone ran ICS on it at some point. If you have an external sd card, at least 8GB, this thread may help-
http://forum.xda-developers.com/showthread.php?p=21439417
you could use cm10.1 instead of the ICS rom mentioned in the thread.
Sent via Monty Pythons Flying Circus

[Q] GT-P1000 Stuck in bootloop

Hello All,
Long time lurker, first time poster (and, as usual, asking for help)
I have a Samsung Galaxy Tab GT-P1000, stock, rooted. Was installing an app yesterday from the play store, when the device rebooted and now it seems to be stuck in a boot loop.
At first I was afraid that it was the dreaded internal SD card corruption issue mentioned here: http://forum.xda-developers.com/showthread.php?t=1463756
However, when connecting with adb, I was unable to locate any references to the error mentioned in the post above :
Code:
<3>[ 4.802004] mmc0: error -110 whilst initialising MMC card
(Also tried the alternative option to list contents of /dev/block and was able to see several references to mmcblk)
Having said that, I haven't yet tried a wipe data/factory reset from the stock recovery because I am not sure if this will wipe my internal SD card contents. I do want to try to save/ copy out my pics etc. if there is a way to do this at all prior to wiping it. (And yes, I am kicking myself hard for not having backed this stuff up.)
I guess what I am asking for is:
a) Is there a way to recover from this without a complete device wipe?
b) If I do need to wipe from recovery, will I lose media/user data on the interal sd card?; and
c) If so, is there a way to retrieve all this data to a PC prior to wiping?
I have also attached the adb logcat file recorded during the bootloop.
Thanks All!!

Resolved
I guess this forum is not quite as alive as some of the others, which makes sense considering the age of this device.
In any case here is a quick summary of what I went thru to successfully get the device working again. (and I still have all my pics/videos )
a) Answer to my first question below - After a loooot of googling, I couldn't figure out a way to recover without a wipe.
b) Answer to my second question - You will NOT lose data on your internal SD card when you do a wipe from (stock) recovery.
c) Answer to third question - There may be, but I was unable to figure it out. I'm fairly certain you can mount the internal SD manually from ADB if you have root and attempt to pull your files to your PC, but my device didn't have a rooted kernel, so I couldn't quite get this done.
Anyway, my other issue was that my Stock recovery was unresponsive as well. On selecting the wipe option for example, the screen would clear itself of all text and just display the Android w/ Exclamation background. I attempted to flash CWM recovery based on the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2430190
However, I ended up with a corrupt screen when attempting to access this new recovery. (Don't know - May be because of improper rooting?)
I was able to successfully restore the device by flashing the stock recovery and ROM based on this thread http://forum.xda-developers.com/showthread.php?t=1133590 ,following the instructions for un-softbricking .
When I booted into recovery and attempted to wipe/factory reset, I got an error.
Code:
rfs format failed on /dev/block/stl10
There was an additional step I had to take, which is clarified further below in the same thread. http://forum.xda-developers.com/showthread.php?p=27979493#post27979493 , which is to flash dbdata as well.
Doing this let me successfully wipe the device, which in turn let me finally get out of the damn bootloop.
Anyway, I hope all this helps someone. Thanks for being a great resource as usual XDA! :good:
Dagrat3One said:
Hello All,
Long time lurker, first time poster (and, as usual, asking for help)
I have a Samsung Galaxy Tab GT-P1000, stock, rooted. Was installing an app yesterday from the play store, when the device rebooted and now it seems to be stuck in a boot loop.
At first I was afraid that it was the dreaded internal SD card corruption issue mentioned here: http://forum.xda-developers.com/showthread.php?t=1463756
However, when connecting with adb, I was unable to locate any references to the error mentioned in the post above :
Code:
<3>[ 4.802004] mmc0: error -110 whilst initialising MMC card
(Also tried the alternative option to list contents of /dev/block and was able to see several references to mmcblk)
Having said that, I haven't yet tried a wipe data/factory reset from the stock recovery because I am not sure if this will wipe my internal SD card contents. I do want to try to save/ copy out my pics etc. if there is a way to do this at all prior to wiping it. (And yes, I am kicking myself hard for not having backed this stuff up.)
I guess what I am asking for is:
a) Is there a way to recover from this without a complete device wipe?
b) If I do need to wipe from recovery, will I lose media/user data on the interal sd card?; and
c) If so, is there a way to retrieve all this data to a PC prior to wiping?
I have also attached the adb logcat file recorded during the bootloop.
Thanks All!!
Click to expand...
Click to collapse

Hi, guys.......new to the process....rooted my galaxy tab p1000 2.2 froyo with z4mod.
Then initially I installed cwm with ROM manager for galaxy tab T because there wasn't any specific model of cwm for p1000.
But but when I switched off and booted recovery, stock recovery always came......I could access cwm only through the ROM manager ("boot into recovery")....and that too if i choose any function it starts to load and when I press home twice it says "replacing stock with cwm" and that goes on forever...
So I installed cwm with Odin as I couldn't access functions like "install" in cwm without going into the loading phase.....but as the process in Odin finished, my tab started to boot and at "galaxy", the sceen got all pixalated and it went till " samsung " and the whole process looped........ Help!

CM not installing\ Can't mount i-sdcard=Help fix my phone?

I tried installing one of the 10 stable versions. I was on stock jw4 with cf+cwm karnel. It started installing and then went into boot in middle for no reason. But it didn't boot. It just kept booting into recovery (not the cwm version i had) with the cm logo.
I tried installing again but it aborted installation every time. (didn't check the log)
I then tried to go back to stock but never boots,in recovery i get a bunch of:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
system unable to Format /data...Internal SD card cannot be mounted
rfs format failed on dev block etc etc etc
I tried all the ways i found here but none helped,worked on it for hours. I also flashed a bunch of stock versions with no luck. All just went to recovery with all these erros. Only thing that actually booted was a very old version stock jp something,got same message on recovery but then booted into...cm10 . I just got the boot and then black screen with buttons looking like they are on.
I then gave up and decided i would install cm and hopefully that would be compatible with what ever was changed since it happened because of it.
I now tried installing all the 10 stable versions and then all the 11snapshots. I either get error 7 or 0 and installation aborted or the same thing that happened the first time-it starts installation and then boots, gets stuck in (cm logo) bootloop and ends up in recovery.
ATM my phone is kind of bricked i guess. How do i fix this?