Related
Several users have complained that they get blank screens and cannot flash new roms to their Nook Color. And sometimes they end up in a recovery bootloop where it will do nothing but boot to recovery no matter what they choose in the boot menu. Sometimes this is due to corrupted partitions on internal memory.
DizzyDen has prepared some .img files that can be burned to emmc to repair some of these issues, and they work well. But some of the files are very large and it takes a little knowledge of adb commands on the part of the users. And some users cannot get adb working on their machines. So I started investigating other solutions, and I have made some tools that work that I hope are user friendly.
Dean Gibson has a thread that describes how to repartition emmc to set the partition sizes for data and media to the user's preference. He repartitions partitions p6 (data), p7 (cache) and p8 (media). In studying his zip, I figured out how to make his tool repair partitions p4 (extended), p5 (system), p6 (data), p7 (cache), and p8 (media). And I was able to add additional commands to also repair partition p1 (boot). I asked Dean's permission to post his tools as modified by me and he agreed. Thanks Dean!
So that takes care of partitions 1, 4, 5, 6, 7, and 8.
Partitions 2 and 3 are very special and one must be very careful with them. Partition 2 is 'rom', which holds information that is specific to the user's device (serial number, etc.), and it is used by the system to set flags for deciding whether to boot to recovery or not and set the boot count that is used to decide whether to do a reset to factory conditions (8 failed boots). Partition 3 is 'factory' and holds the factory.zip file used by the 8 failed boot reset (if you want to learn more about the 8 failed boot reset, go to my tips thread linked in my signature). It also holds a backup of the device information in partition 2. So it is possible to repair partition 2 if partition 3 is still intact.
A few users have somehow managed to flash Nook Tablet ROMs to their Nook Colors and really messed up partition 4. (Edit: and now I know how it happened, some idiot recommended that they remove the first line of the updater script. NEVER do that! That line is a safety check to make sure you are flashing to the right device. You can also defeat the safety check by using an old CWM that has the toggle, 'disable asserts'. Never do that either.) And since partition 4 is the extended partition that holds partitions 5, 6, 7, and 8, they get messed up too. To repair those partitions along with partition 1, use CWM recovery to flash the two zips attached below. Be warned that everything in emmc media (p8) will be wiped out, so you may want to back that up first if you still can. The first zip to flash is 'NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip'. It will recreate those partitions on emmc. As soon as you have sucessfully flashed that zip, you must reboot the Nook Color back to CWM so that the updated partition table is read by CWM. Then you need to flash 'NookColor-emmc-format-partitions-5-6-7-8.zip' (partitions 1 and 4 do not need formatting). It will format the newly created partitions to the correct structure. Now you can use CWM to restore an earlier nandroid backup or flash your favorite ROM (including stock, get version 1.4.3 that I have modified to be flashable with CWM here, or DizzyDen has posted some excellent 1.4.1 stock ROMs here). If you are going to flash a stock ROM, you must be sure to use the format zip or the stock ROM will not boot properly.
If you are in a recovery bootloop, the first thing I recommend trying is to use my CWM version 5.5.0.4 bootable SD that is discussed in my tips thread linked in my signature and has been modified to help get out of some kinds of recovery flag bootloops. If you are in a recovery bootloop that just hangs, it may get you out of it after exiting my CWM with the 'reboot' command in the menu. But if you are still in the loop after doing that, it may be because your device info is missing or corrupted in partition 2. It will not boot to a ROM without this info. (Specifically, it needs a file in /rom/devconf named DeviceID. It is a text file with your 16 digit serial number in it followed by a line feed, 17 bytes.) Try flashing with CWM my 'NookColor-emmc-repair-partition-2.zip' attached to this post to recreate that info. But I recommend this as a last resort, since messing with that partition is risky. That zip will recreate the partition, reset the flags and copy your device specific information from partition 3. But your partition 3 must be intact for this to work. If it is not, the zip will abort and do nothing.
Additionally, for those that do not want to use CWM, I have made a bootable SD that has an older version of TWRP here. Newer versions of TWRP will return an error message when trying to flash these zips. It also has been modified to get you out of some kinds of bootloops.
Two points of information. First, I have included a temporary copy of CWM 5.5.0.4 on the boot partition of my repair so that if tries to reboot to emmc before you put a ROM on it, it goes to CWM. It will be removed as soon as you restore a backup or flash a ROM. Second, the new partition scheme created with my zip is for the original Nook Color's 1GB data and 5GB media. If you want one of the other schemes (5GB data/1GB media or 2GB data/4GB media) go to Dean Gibson's thread and flash his zips after you have repaired your system with mine. See his thread here.
I'm adding a little extra information about emmc partition structure for those interested. With any MBR disk there can be a maximum of four primary partitions. So to have more than four partitions the last primary partition is created as an extended partition so multiple logical partitions can be made inside it. The emmc structure is: p1 (boot, fat, primary), p2 (rom, fat, primary), p3 (factory, ext3, primary), p4 (extended, going from end of p3 to end of the disk), p5 (system, ext2, logical, inside the extended), p6 (data, ext3, logical, inside the extended), p7 (cache, ext3, logical, inside the extended) and p8 (media, fat, logical, inside the extended).
You save my nook color
Thank you so much. My serial number and other information were recovered successfully. Without those information I could not boot into any rom. If you cannot boot into ROM after following the first 2 steps, try recover partition 2. It works for me.
:laugh::laugh::laugh::laugh::laugh:
Thanks
My nook has been stuck in a "will not boot" state for about a week. I could run CWM and cyanoboot, but when ever I tried to boot CM I would get stuck at the "loading..." screen. I tried loading both CM7 & CM9 but neither one would boot.
I ran both repair scripts, reloaded CM7.1 and success!
Thanks Leapinlar! :good:
THANK YOU!!!!!!
Right from my 1st install I couldn't get the bar at the bottom of the screen, which made using the Kindle app more than a little difficult. This finally cleared everything off so I could start with a clean slate, and BINGO! I know have the bottom bar on all the screens. I assume when I go in to the Kindle app it will be ok now also (I just have to format a 16gb microSD and put in the Nook Color 1st).
I can't thank you enough!!!!
Ugh! Tried this method too, and I still cannot get the nook to boot into CWR or CWM. I tried the 8 boots thing too, but I don't know if I ever did it right because I have cyanogen mod installed on emmc. Not sure how to repair the partition if I cannot even boot into anything that allows me to flash the zip to the chip. I thought it may be the sd, but the sd cards work on my other nook. I have now basically dissembled my nook color trying to find any other solution I wish I knew what happened in the first place.
czarofthefrozentundra said:
Ugh! Tried this method too, and I still cannot get the nook to boot into CWR or CWM. I tried the 8 boots thing too, but I don't know if I ever did it right because I have cyanogen mod installed on emmc. Not sure how to repair the partition if I cannot even boot into anything that allows me to flash the zip to the chip. I thought it may be the sd, but the sd cards work on my other nook. I have now basically dissembled my nook color trying to find any other solution I wish I knew what happened in the first place.
Click to expand...
Click to collapse
Did you try my version of the CWM bootable SD card? It is on my tips thread and has been modified to boot in certain types of recovery bootloops. Unless you get CWM running you cannot flash things to internal memory. And depending on where in the boot process it hangs, you may not be able to get adb working to put things there either. And the 8 failed boots will not work unless you have stock recovery still on emmc.
Sent from my NookColor using Tapatalk
leapinlar said:
Did you try my version of the CWM bootable SD card? It is on my tips thread and has been modified to boot in certain types of recovery bootloops. Unless you get CWM running you cannot flash things to internal memory. And depending on where in the boot process it hangs, you may not be able to get adb working to put things there either. And the 8 failed boots will not work unless you have stock recovery still on emmc.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Yup. Tried the card. I believe I replaced the emmc with cyanogenmod back in the day. Starts, goes to loading, turns black, then done. Cannot do anything after that. Bummer, sounds like it is actually toast.
czarofthefrozentundra said:
Yup. Tried the card. I believe I replaced the emmc with cyanogenmod back in the day. Starts, goes to loading, turns black, then done. Cannot do anything after that. Bummer, sounds like it is actually toast.
Click to expand...
Click to collapse
If you can get adb working while it is sitting there black, you can push the stock recovery files to partition one. Then you may be able to do the 8 failed boots. You can extract the stock recovery files from my zip in my tips thread.
leapinlar said:
If you can get adb working while it is sitting there black, you can push the stock recovery files to partition one. Then you may be able to do the 8 failed boots. You can extract the stock recovery files from my zip in my tips thread.
Click to expand...
Click to collapse
Worth a shot. Have nothing more to lose other than time. Maybe adb will work with you card in it. It didn't work with everything else I tried.
OMG OMG thank you soooo much for this thread , you saved my reading addict self from going insane ......
You've done a great job on collecting all of these useful things, especially for those who are stuck with their Nook Color boot looping. (I was once that guy) Dean helped me out with his data zips as well way back! Thanks for all this! :good: :victory:
Much thanks, leapinlar. Restored a nandroid with TWRP that was corrupted and lost my boot partition. I used your first 2 repair zips and I'm back in business. Your many contributions are greatly appreciated.
Mike T
OMG! Thank you so much for putting this up! Back at the beginning of the year I was having problems with my NC not going into USB Mode and only showing a black arrow when trying to load books and following this finally fixed it. Great write-up and instructions, thanks for the hard work.
I've been trying to restore my NOOK for about 2 weeks and this post has gotten me the farthest but i'm stuck at the point where my nook will start up, the "Read Forever" splash screen will come up and then it attempts to recover the system since i see an greenish Android screen come up for a second and then i get an error screen saying "Install Failed" with an image of a nook with an exclamation point in it's screen. I'm assuming i've really messed the nook up but here is where I am.
I've reformatted the partitions using your 1-4,5,6,7,8 zip
Rebooted to recovery
Formatted partiions 5,6,7,8 with your zip
Flashed your 1.4.3 stock rom
At this point I can't get any further since it appears something else is wrong and i didn't want to attempt the reformatting of partition 2 without asking if there is anything else i should try. Any help would be appreciated.
Thanks
jmiklus01 said:
I've been trying to restore my NOOK for about 2 weeks and this post has gotten me the farthest but i'm stuck at the point where my nook will start up, the "Read Forever" splash screen will come up and then it attempts to recover the system since i see an greenish Android screen come up for a second and then i get an error screen saying "Install Failed" with an image of a nook with an exclamation point in it's screen. I'm assuming i've really messed the nook up but here is where I am.
I've reformatted the partitions using your 1-4,5,6,7,8 zip
Rebooted to recovery
Formatted partiions 5,6,7,8 with your zip
Flashed your 1.4.3 stock rom
At this point I can't get any further since it appears something else is wrong and i didn't want to attempt the reformatting of partition 2 without asking if there is anything else i should try. Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Do the partition 2 repair. That is what is messed up and causing the reboot.
Sent from my Nook HD+ using Tapatalk
leapinlar said:
Do the partition 2 repair. That is what is messed up and causing the reboot.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
I've tried the partition2 zip and received an error trying to mount the factory partition. Status 7 was the error code. Is there a way to fix this?
jmiklus01 said:
I've tried the partition2 zip and received an error trying to mount the factory partition. Status 7 was the error code. Is there a way to fix this?
Click to expand...
Click to collapse
Oh, that is really bad news. That means your partition 3 is corrupted and there is no way to retrieve your device info, like serial number, etc. PM me and maybe I can help you get it partly working, but much of the device info is lost if that partition is truly corrupted.
Sent from my BNTV600 using Tapatalk
Restore NC back to stock
View attachment 1500490
leapinlar said:
Oh, that is really bad news. That means your partition 3 is corrupted and there is no way to retrieve your device info, like serial number, etc. PM me and maybe I can help you get it partly working, but much of the device info is lost if that partition is truly corrupted.
Sent from my BNTV600 using Tapatalk
Click to expand...
Click to collapse
I've been trying to restore my daughter NC back to stock for couple months now and no success.
I did flash the P 1-4-5-6-7-8.zip and got this message after reboot:
"CWM-based Recovery v5.5.0.4
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
during the reboot, there is a menu option to hit "n" for reboot mode option. when i hit "n" it gives me (attachment).
but it won't let me move up or down to select except for the 1st option
Help would be very appreciated
big64dave said:
View attachment 1500490
I've been trying to restore my daughter NC back to stock for couple months now and no success.
I did flash the P 1-4-5-6-7-8.zip and got this message after reboot:
"CWM-based Recovery v5.5.0.4
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
during the reboot, there is a menu option to hit "n" for reboot mode option. when i hit "n" it gives me (attachment).
but it won't let me move up or down to select except for the 1st option
Help would be very appreciated
Click to expand...
Click to collapse
During reboot it should automatically go to CWM because everything else is wiped. The boot menu only lets you make the first choice because that is all that is there, everything else is wiped. You need to continue to use the CWM to flash the format zip next. Then you can flash a ROM. If the CWM that pops up is not working, use the bootable CWM SD.
leapinlar said:
During reboot it should automatically go to CWM because everything else is wiped. The boot menu only lets you make the first choice because that is all that is there, everything else is wiped. You need to continue to use the CWM to flash the format zip next. Then you can flash a ROM. If the CWM that pops up is not working, use the bootable CWM SD.
Click to expand...
Click to collapse
Thx for replied, the Nook just stock on loading and it won't let me do anything except for power up and down
Evening,
After trying nearyl everything I found online to get my phone back into a working state I finally gave up and decided to ask
you for help.
So, it all began with me trying to flash the Jelly Bean Port onto my SGS in the hope it would fix my constant crashes and other problems
I had after another flash.
I got it working at some point, but it did not react when I plugged it in the usb port as mass storage device or any other mode for that matter.
So I tried some other solutions.
A couple tries later i started getting the "cant mount /dbdata" error which i fixed with a solution from this forum using a dbata.tar as PDA, using the JW4 firmware.
However because I wanted the usb to work I tried again to get jelly bean to run, without success.
I'm no unable to boot the phone passed "Enter your password to decrypt storage" or in any other mode.
When flashing I keep getting "Failed to mount /data" which seems to disappear at times when the external sd is inserted.
My Computer regocnizes the Phone as two different drives, even when i remove the sd...
So yeah.
The moral of the story is: I cant get the phone to run on any mode except jellybean and there without usb connection, if i get passed the decrypt thing.
Currently all flashing leads me to the recovery screen saying:
"Can't mount /data " and "Cache wipe failed" after that it just bootloops.
So, can anyone help me out?
P.S. I can at all times enter recovery and download mode.
Hey
If u can enter download mode, why dont u flash 2.3.6??that should clean all your problems..
Plus if you upgrade to JB your external sd-card wont be mounted to ur system...(you cannot alter any data directly to your external sdcard...
There are 3 ways to solve your prob..
1.use CWM..
--goto mounts and storage, then hit external sdcard..
2.use your external memory card directly with ur system..that means without your phone
3.(long method)
Transfer ur data to internal sdcard then use a file manager and transfer to external memory card
Cheers
If I Helped, dont mind Hitting the Thanks button...
Flashing an old Stock Rom mostly fixes all problems for me and should do the same for you
Sent from my GT-I9001 using xda app-developers app
Hi,
Thanks for the answers.
Flashing an old Stock Rom mostly fixes all problems for me and should do the same for you
Click to expand...
Click to collapse
I tried this approach and flashed the JVU Version from samfirmware.
It leads to the following error:
Code:
Failed to mount /sdcard (file exists)
(...)
Format_volume: rfs format failed on /dev/block/mmcblk0p2
During the boot up, after the first flash.
Note: The external SD-Card was not in the phone, as well as the sim card.
After that it starts bootlooping.
If I insert the external SD-Card before the flashing process i only get:
Code:
Format_volume: rfs format failed on /dev/block/mmcblk0p2
And the Phone starts to bootloop again.
I've tried to google this and I get two reactions:
The internal SD is fried.
Format the internal SD using CWM.
I believe I did try the second approach, but i would greatly appreciate a short guide on how-to properly format my internal SD
There are 3 ways to solve your prob..
Click to expand...
Click to collapse
I was under the impression they had fixed that bug in V6.
Anyway, it's not the real problem since I would rather get my phone to work again, before I go ahead and try out jelly bean again.
The ics semaphore.tar odin kernel from the semaphore thread has worked for everyone I've suggested it to.
For some reason it seems to work where other flashable packages don't, worth a try.
Sent from horseback.
First of all I flash stock firmware. / 3 PDA files, MODEM, CSC / odin with the pit512 and Re-partition.za second is that the flash / ICS, JB / clearing script to use the kernel, then the full wipe and cwm JB installation ....
adytum said:
The ics semaphore.tar odin kernel from the semaphore thread has worked for everyone I've suggested it to.
.
Click to expand...
Click to collapse
Did you mean this Semaphore Thread?
If so, just tried it, didnt work, still get the same error as before:
Code:
Format_volume: rfs format failed on /dev/block/mmcblk0p2
misacek said:
First of all I flash stock firmware. / 3 PDA files, MODEM, CSC / odin with the pit512 and Re-partition.za
Click to expand...
Click to collapse
At this Point, I get the first error concering the formating, see above.
If I still continue and manage to get JB to work (I event tried the kernel cleaning script). I get locked out because of this "Enter password to
decrypt storage" Error. Which is known to be fixed by performing a factory reset, which I cant do, because of the first error.
f_erin said:
I get locked out because of this "Enter password to
decrypt storage" Error. Which is known to be fixed by performing a factory reset, which I cant do, because of the first error.
Click to expand...
Click to collapse
try and enter any password five times until prompted that this will wipe the card, than you should be able to do so
So, today I decided to buy a new smartphone after one last try of getting my old one to work.
I used the default guide to flash JellyBean and now it works ...
I guess it was scared or something, I'll keep using it to check of fluently it works for now and bought and sd reader to solve the usb issue.
So this thread can be closed.
Thanks to all for their tips.
Hello boys and girls,
I think the internal SD card of my i9000 is corrupted. I've tried everyting: wiped/factory reset, reinstalling Cyanogenmod10, installing Stock ROM, installing stockrom with re-partitioning on etc. Nothing works. I'm using odin to reinstall the stock ROM. 'Uploading' the stock ROM to my phone goes well, but then when I restart and android is installing, I get error messages like:
/dev/block/mmcblk0p2 or
/dev/block/mmcblk0p1
After reading a lot on XDA, my conclusion is: broken internal storage.
Now I want to install everything on my external SD. So I bought a 8GB cat10 SD card.
I followed the instruction given in this youtube video (the error in the video is the same as mine): http://www.youtube.com/watch?v=zdMhYYdMB08 Unfortunatly this didnt help. Reading the Youtube comments it seems this method only works when you're SD card is totally broken. Mine is not I guess
Then I found this XDA-post: http://forum.xda-developers.com/showthread.php?t=1893354 Seems very promising, but I seem to get stuck on '-- Extract initramfs from zImage ( https://github.com/mistadman/Extract-Kernel-Initramfs )'. I;ve got a virtual machine running Ubuntu. When I start the script, nothing happens..... the terminal just closes.
The easiest solution for my problem would be a ROM that is altered to directly install on my external SD. I red somewhere that ROMS like that exist. Can't seem to find one though.
Well.. thanks for reading my post, and accept my appologies for my bad english. You can probably notice I'm not a native speaker.
Does someone have a solution for me? Maybe know of a good thread?
Thanks in advance!
Greatings, Eldoro
eldoro said:
I think the internal SD card of my i9000 is corrupted.
Click to expand...
Click to collapse
check out My Android Solutions and My Android Collections on How to Flash a Rom with a broken SD card
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.
Corrupt internal storage
xsenman said:
check out My Android Solutions and My Android Collections on How to Flash a Rom with a broken SD card
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.
Click to expand...
Click to collapse
Thanks for your advice. There are a lot of solutions in 'My android solutions'. I have taken another look at my error message, but it's a bit different then the onces that a there. So I don;t know wich one to pick. I will attach a screenshot of my error message:
Trying the other link you gave me (My android Collections), I don't really understand the second step. See my remarks in red:
[I]ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd ) (How do I do this? Where is de adb directory? Where do I start cmd, on my pc or on my android? What is a adb shell?)
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip
[/I]
Hope you can point me in the right direction.
screenshot
HEre is the link to my screeshot. Didnt seem to work in my previous post:
postimage.org/image/8451hvzuz/
Greatings, Eldoro
eldoro said:
HEre is the link to my screeshot. Didnt seem to work in my previous post:
postimage.org/image/8451hvzuz/
Greatings, Eldoro
Click to expand...
Click to collapse
what are you trying to flash with 3e recovery, its better to use CWM recovery, just flash a semaphore kernel to get root and CWM
still problems with semphore
xsenman said:
what are you trying to flash with 3e recovery, its better to use CWM recovery, just flash a semaphore kernel to get root and CWM
Click to expand...
Click to collapse
I've flashed smaphore kernel with Odin. I also downloaden Cyanogenmod-10-20121017.
I started my phone with the 3 button combo and got into CMW 6. Then I mounted USB storage and tried to transfer CM-10 to internal storage. While transfering my phone reboots...
I then succesfully copied the CM-10 file to my external SD. When I install the zip (after a wipe data/factory reset and wipe cache) I get the following error: postimage.org/image/5ma4nnnhj/
When I restart my phone I can't get into CMW again... so I flash semaphore again.
When I;m in CMW again I tried some thing... maybe its interesting for you to see:
After I wipe data/ factory reset, and I go to advance -> show log, I see the following errors: postimage.org/image/ygj9q6o1v/
Another example. In CWM, when I try to mount /data and /system, I get the following error: postimage.org/image/hol1hhhyd/
Mounting /data or /cache goes doesnt give any problems.
Hope this gives you some more insight..
eldoro said:
I've flashed smaphore kernel with Odin. I also downloaden Cyanogenmod-10-20121017.
Click to expand...
Click to collapse
The root cause of your problem is status 0 ( see My Android Solutions) likely you have flashed an ICS or JB kernel on a Gingerbread , thus having the wrong version of CWM on your phone . go here My Android Collections and download the correct kernel to use according to the firmware you are using
Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
(Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.)
xsenman said:
The root cause of your problem is status 0 ( see My Android Solutions) likely you have flashed an ICS or JB kernel on a Gingerbread , thus having the wrong version of CWM on your phone . go here My Android Collections and download the correct kernel to use according to the firmware you are using
Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
(Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.)
Click to expand...
Click to collapse
I have flashed the semaphore GB kernel 2.7.4 (first pulled out battery, ext sd and hold powerbutton for 60 seconds). Getting other errors now:
postimage.org/image/4pjqlcgb7/ -> screenshot initial booting in CMW
postimage.org/image/8i4rltz7r/ -> screenshot trying tot install zip
Then I flashed Gingerbread (I9000XXJVU_I9000OXAJVU_OXA) -> pda, modem and csc file, partitioning unchecked). After flashing, android keeps restarting on this screen: postimage.org/image/o5ojzxvnr/
Then I pull out battery again, hold powerbutton and power on my phone again. Then I get this error message: postimage.org/image/ecnm34gmf/
I then flash again with semaphore GB 2.7.4. When I restart my phone I don't get past the first 'Galaxy S' screen....
eldoro said:
When I restart my phone I don't get past the first 'Galaxy S' screen....
Click to expand...
Click to collapse
Do a clean flash, meaning you will wipe everything and format your SD card too, since you will have CWM recovery
1) First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power
button for a minute, than powerup without SIM and Ext.SD Card....
2) use combo keys to get into CWM recovery
a) wipe everything, data, cache, dalvik cache in advance
b) go into > mounts and Storage> format everything (except boot) repeat ..do it twice....than pull out battery and use combo keys to boot into download mode ( you will lose everything in your phone by doing this, hope you have backed up your contacts, images and game data etc) If you did not mout to USB storage first and copy the entire SD card to your PC first)
3) connect to PC, use ODIN3 and flash the JVU ROM with a 512 PIT file with repartitioning checked
Once it has booted , check your phone, check your SD card ( so that everything is functioning)
4) Flash the GB semaphore kernel and check again all is functioning, backup your efs before you try custom roms like this
xsenman said:
Do a clean flash, meaning you will wipe everything and format your SD card too, since you will have CWM recovery
1) First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power
button for a minute, than powerup without SIM and Ext.SD Card....
2) use combo keys to get into CWM recovery
a) wipe everything, data, cache, dalvik cache in advance
b) go into > mounts and Storage> format everything (except boot) repeat ..do it twice....than pull out battery and use combo keys to boot into download mode ( you will lose everything in your phone by doing this, hope you have backed up your contacts, images and game data etc) If you did not mout to USB storage first and copy the entire SD card to your PC first)
3) connect to PC, use ODIN3 and flash the JVU ROM with a 512 PIT file with repartitioning checked
Once it has booted , check your phone, check your SD card ( so that everything is functioning)
4) Flash the GB semaphore kernel and check again all is functioning, backup your efs before you try custom roms like this
Click to expand...
Click to collapse
After finishing step 3 my phone tries to install android but comes up with a Error. It only shows for a few seconds, so didnt have time to take a screenshot. It said someting about 'can't find directory samsung/music' ...'vox'.... Then the phone restarts and the samsung intro video starts but the video crashes after a few seconds and my phone restarts again. And again and again...
Not much luck so far )-:
eldoro said:
. It said someting about 'can't find directory samsung/music' ...'vox'.... Then the phone restarts and the samsung intro video starts but the video crashes after a few seconds and my phone restarts again. And again and again...Not much luck so far )-:
Click to expand...
Click to collapse
Fundamentally your problem seems to be related to an SVOX installation ( text to speech engine) you must have used when your phone was functioning ...which seems to be mounted and giving you this error
E:copy_dbdata_media:Can't unmount "/dbdata"
E:Format_volume failed to unmount "/dbdata"
so you need to get back into CWM > mounts and storage> unmount everything and also format everything including boot, after that , ( DO NOT BOOT phone after doing this)
after this pull out battery and this time include i9000 JVU bootloader + JVU + 512 PIT ( update bootloader and repartition TICKED and reboot UNTICKED )
after that flash again the JVU ROM and reboot phone
If this fails, we may need to downgrade the ROM to 2.2 and use a speedmod kernel and try, basically, your Internal SD partition is stuck on this one dbdata partition and you need to get it formatted to solve your SD problem ( looks like you are in luck as someone else had this problem earlier , read this thread and solved it.
suggest you use a note book to note down what you are doing (step by step) and what was the result to get to the bottom of solving this , once and for all, will be useful for others who may have this problem.
xsenman said:
Fundamentally your problem seems to be related to an SVOX installation ( text to speech engine) you must have used when your phone was functioning ...which seems to be mounted and giving you this error
E:copy_dbdata_media:Can't unmount "/dbdata"
E:Format_volume failed to unmount "/dbdata"
so you need to get back into CWM > mounts and storage> unmount everything and also format everything including boot, after that , ( DO NOT BOOT phone after doing this)
after this pull out battery and this time include i9000 JVU bootloader + JVU + 512 PIT ( update bootloader and repartition TICKED and reboot UNTICKED )
after that flash again the JVU ROM and reboot phone
If this fails, we may need to downgrade the ROM to 2.2 and use a speedmod kernel and try, basically, your Internal SD partition is stuck on this one dbdata partition and you need to get it formatted to solve your SD problem ( looks like you are in luck as someone else had this problem earlier , read this thread and solved it.
suggest you use a note book to note down what you are doing (step by step) and what was the result to get to the bottom of solving this , once and for all, will be useful for others who may have this problem.
Click to expand...
Click to collapse
Tried your first advice. Couldnt unmount SD Card and didnt saw a boot partition to unmount.... Flashed with JVU bootloader, JVU, 512pit like you said. Then flashed again JVU. Got the same result... didnt work. Still error messages.
Then flashed with ROM 2.2 and speedmod kernel. Could format the SD Card with CWM now... Again no result in the end. Didnt get the error messages though when android install... but still keeps rebooting when booting.
Then used the EZbase recovery kit, like described in the thread you gave me (althoug the thread is a bit old and hard to understand). Flashed everything in the kit with EZodin. Result: no error messages after reboot, but I can see it doesnt finish the first install. Then it reboots and gets stuck on the Samsung video..
Now trying to connect to my phone via ADB. Downloaden the ADB toolkit. Want to try this:
adb shell
mount /sdcard
su
parted /dev/block/mmcblk0
rm 1
rm 2
rm 3
quit
Its hard to understand if above commands fixed the problem in the thread you gave me... it's not very well described..
Do you have tips to connect to my phone through ADB? Downloaden ADB-toolkit and started adb-toolkit-main.cmd.
Reinstalled Samsung USB drivers..tried to connect in download mode and in recovery (with different CMW versions). Installed the drivers included in ADB-toolkit through zadig.exe.. tried in download mode and recovery...
eldoro said:
Do you have tips to connect to my phone through ADB? Downloaden ADB-toolkit and started adb-toolkit-main.cmd.
Reinstalled Samsung USB drivers..tried to connect in download mode and in recovery (with different CMW versions). Installed the drivers included in ADB-toolkit through zadig.exe.. tried in download mode and recovery...
Click to expand...
Click to collapse
suggest you just flash the Ezbase gingerbread rescue kit again, might solve it since your error message is not there anymore
xsenman said:
suggest you just flash the Ezbase gingerbread rescue kit again, might solve it since your error message is not there anymore
Click to expand...
Click to collapse
Flashed with ezbase_recovery_kit_gb. Powered down and flash the stock kernel first. Then flash with partitioning ticked. After reboot it starts to install, but reboots. Then I don;t get past the first Samsung screen. Installed the rooted kernel and rebooted.. didnt got passed the Samsung screen.
Then powered down again and flashed the ezbase_gb bootloader, After that I flashed again with PDA, SCS, Phone and pit (repartioning ticked). Rebooted and the phone starts installing but reboots when doing so. Then again don't get past Samsung Screen.
I;ve made a movie of the initial install. I don't get red error messages, but looked at the video in slomotion and noticed there is still a error message in yellow. Got you a screenshot: http://postimage.org/image/gxhu8tvf7/ Sorry for the lack of focus, it's hard to read.. Think the path in the screenshot is /system/csc/KOR/system
eldoro said:
Think the path in the screenshot is /system/csc/KOR/system
Click to expand...
Click to collapse
looks like all your earlier problems is solved but strange its not booting, try flashing a JVU Bootloader with an 803 PIT ( RePartition UNTICKED) from My Android Collections
after this try a custom ROM, meaning flash a semaphore kernel, after that do the wipes, after that mount to USB storage and copy i9000 CM 9.1 stable to SD card and flash it
xsenman said:
copy i9000 CM 9.1 stable to SD card
Click to expand...
Click to collapse
Did like you described. Didnt restart/reboot after flashing the bootloader and pit, went straight on to flashing semaphor... Hope I interpreted your description well....
Only when copying CM 9.1 to my phone, my phone restarts when it's halfway.... Tried it a few times, but can't copy the file to my phone...
eldoro said:
Did like you described. Didnt restart/reboot after flashing the bootloader and pit, went straight on to flashing semaphor... Hope I interpreted your description well....
Only when copying CM 9.1 to my phone, my phone restarts when it's halfway.... Tried it a few times, but can't copy the file to my phone...
Click to expand...
Click to collapse
you can try any other way to do it, you can even copy it in your EXt SD card and flash from there..which ever suits you.
Bottom line, the errors are not there, so you may just flash the ROM, twice or thrice to get it working
xsenman said:
you can try any other way to do it, you can even copy it in your EXt SD card and flash from there..which ever suits you.
Bottom line, the errors are not there, so you may just flash the ROM, twice or thrice to get it working
Click to expand...
Click to collapse
Installed CM9.1 from external SD card. Installing zip finishes without errors, but on boot it gets stuck on the cyanogenmod video. Reinstalled a few times, but no succes. Then flashed with semaphore Jellybean kernel and tried installing CM10nightly... no succes either didnt finisch install... Then flashed semaphore ICS kernel again and tried again with CM9.1.. Result: not errors installing, but freezes on boot...
Then I flashed again with cm9.1 and looked in the log after installing te zip. Seems there are errors! Screenshot of log: http://postimage.org/image/cp1devyfl/
eldoro said:
Seems there are errors!
Click to expand...
Click to collapse
Basically, it is CWM errors and not what you should solve first, you need to get your phone booting, so get back to Stock ROM , try Darkys Resurrection with PIT, IF all goes well try for CM 7 first...DO not Flash a CM kernel First, always flash the ROM and only after that, use the relevant kernel for that ROM
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
My Galaxy Note N7000 was on the Jelly Bean 4.1.2 LM5 (HK) firmware with "PhilZ-cwm6-ZSLM5-OZS-4.35-signed.zip" installed.
Phone internal memory was repartitioned to 10.9GB for /system and 2 GB for /data since I store most of my files on the microSD card anyway.
The phone was working nicely although I did experience a boot loop problem when I first flashed it because I changed the phone ID with Titanium Backup, so I did a wipe to get out of the boot loop.
But today in my haste to pull the SIM card out of the phone I forgot to completely shutdown my phone before pulling the battery out, and as expected the boot loop returned.
Searched around xda and it seems that everyone's solution is to wipe the phone to factory default.
The problem was that I haven't backed up my phone for quite a while and I wasn't willing to wipe the phone again and lose all of my data if I can avoid it. :crying:
So after fiddling with the phone, at recovery I noticed that it wasn't able to mount the /data partition, so I fired up adb shell and tried to mount it manually by using "mount /dev/block/mmcblk0p10 /data" but it spouted out an IO error.
Apparently, my phone was stuck in the bootloop because it wasn't able to mount the /data partition because of a file system error which happened because of the unclean shutdown/battery pull.
Figuring that my data is toast anyway if I wiped the phone to get past the bootloop, I experimented with these commands :
Code:
adb shell
umount /data
e2fsck -y /dev/block/mmcblk0p10
e2fsck reported that the journal was corrupted and there was a gazillion of 'multiply-claimed block' errors on the partition, but finally after an hour it finished but with some note that there's is still some error in the lost+found null node something.
I tried to mount the /data partition with Touch Recovery again and it worked, so I restarted and it gets past the boot screen and all my data are still intact.
I am now flashing the new UBLSF and PhilZ new kernel with bootloop fix, I hope that gets rid of the bootloop problem for good.
This seems similar to the problem and solution posted here : http://forum.xda-developers.com/showthread.php?t=2040107
Hope my experience is useful to others who experience similar problem
Thank you. Really helpful.
Enviado desde mi BlackBerry Runtime for Android Apps usando Tapatalk 2
this also happen when the battery is completely empty and the phone perform unclean shutdown this is why you must stop using your phone at 1% battery to prevent this stupid bootloop
zerenx said:
But today in my haste to pull the SIM card out of the phone I forgot to completely shutdown my phone before pulling the battery out, and as expected the boot loop returned.
Click to expand...
Click to collapse
I did that too, then I fixed data partition, yet since that incident. It happens several times that I find my phone shut (even though the battery is full), then the phone is boot looping. I can't understand the reason for this.
Hi, yesterday my phone suddenly restart few times before stuck at the samsung boot animation. Until today my GNote unable to get pass the boot animation. Is there any way to fix this without data wipe because I didn't expect this would happen so I haven't backup my data yet. I'm using samsung latest official Jelly Bean. Non rooted. Last activity before it happen, playing games & update few apps in play store. This is the first time I post in this forum. Sorry if there's any mistake I've made.
Can you connect your phone to the PC? And try to use the phone while keeping it plugged in to charge. How old is your battery? If you can conncet to the PC, you can take a copy of your data.
I can copy files from sdcard. But not from internal storage. And I actually need to backup my sms, call log, etc.. which need to able to boot the phone. battery is almost 1 year already.
Can you use the phone while keeping it plugged in? There must be an issue with some app, maybe after updating it, any app you suspect?
I no longer can use the phone since it stuck at samsung boot animation there. And I can't really remember which apps I was updating.
thank you! this worked for me. so glad i didnt need to spend half a day reloading everything!
i didnt even need to go to adb. i used the console from CWM
you should mention that one needs to mount the volumes of interest first in order to discover the /dev/block name (and then umount). a la http://forum.xda-developers.com/showthread.php?t=2165870
FYI:
i WAS able to mount /data with cwm utility. but when i tried e2fsck -n, it threw a lot of complaints, so i did it again with a -y, and it rebooted fine.
i also tried browsing around /data with Aroma from CWM. some data/* i could view, but it froze when i tried to look in the delvik folder.
is there a more convenient utility to fsck the whole system everything?
you said, "now flashing the new UBLSF and PhilZ new kernel with bootloop fix". i have PhilZ-cwm6-XXLT4-OXA-x.xx.x-signed.zip. so is there a better cwm i should use to prevent future bootloop?
what is UBLSF?
gnormal said:
thank you! this worked for me. so glad i didnt need to spend half a day reloading everything!
i didnt even need to go to adb. i used the console from CWM
you should mention that one needs to mount the volumes of interest first in order to discover the /dev/block name (and then umount). a la http://forum.xda-developers.com/showthread.php?t=2165870
Click to expand...
Click to collapse
Glad that helps.
At my device, the /data partition is always located at the /dev/block/mmcblk0p10 so I didn't think it was necessary to mention it. Of course, if you repartition your device then the block might change but I guess you should be advanced enough when you've been playing with the partition.
gnormal said:
you said, "now flashing the new UBLSF and PhilZ new kernel with bootloop fix". i have PhilZ-cwm6-XXLT4-OXA-x.xx.x-signed.zip. so is there a better cwm i should use to prevent future bootloop?
what is UBLSF?
Click to expand...
Click to collapse
UBLSF refers to official Samsung firmware Jelly Bean 4.1.2 for Trinidad and Tobago (N7000UBLSF_N7000UUBLSF_TTT).
But no, even that firmware isn't immune to the bootloop, I still experienced one bootloop with UBLSF firmware.
Thankfully I have this thread so I was able to recover my data intact in just a few moments, would've forgot the steps without this thread. :laugh:
It works!
zerenx said:
So after fiddling with the phone, at recovery I noticed that it wasn't able to mount the /data partition, so I fired up adb shell and tried to mount it manually by using "mount /dev/block/mmcblk0p10 /data" but it spouted out an IO error.
Apparently, my phone was stuck in the bootloop because it wasn't able to mount the /data partition because of a file system error which happened because of the unclean shutdown/battery pull.
Figuring that my data is toast anyway if I wiped the phone to get past the bootloop, I experimented with these commands :
Code:
adb shell
umount /data
e2fsck -y /dev/block/mmcblk0p10
e2fsck reported that the journal was corrupted and there was a gazillion of 'multiply-claimed block' errors on the partition, but finally after an hour it finished but with some note that there's is still some error in the lost+found null node something.
I tried to mount the /data partition with Touch Recovery again and it worked, so I restarted and it gets past the boot screen and all my data are still intact.
Hope my experience is useful to others who experience similar problem
Click to expand...
Click to collapse
I thank you from the bottom of my heart! You saved my data!
I was experiencing problems with the Note (rooted, CWM recovery, Philz kernel) and space on the internal memory, so I wiped the Cache and Dalvik partitions (I've done that many a times to be casual about it). The phone restarted thereafter, but went dead all of a sudden, forcing me to do a hard reset. It went into a boot loop, and I could not revive it.
Luckily, I found this thread, and after looking through various other links, I was able to download ADB (without the SDK). Somehow, I could not get ADB to see the device in the download mode (vol down + middle button + power), but it was visible in the recovery mode (vol up + power + middle). [Edit: I ended up taking the necessary steps in Recovery mode after all].
I had been able to mount /data from CWM Touch recovery, but when I tried to backup, the process had been exiting on reaching the /data folder. So I checked the unmounted volume as you had indicated, and it did find some errors! I checked all the other unmounted volumes for good measure, and they turned out to have no errors. (Actually, as I didn't know which block device referred to each of them, I checked with the 'mount' command both before and after mounting/unmounting them from Touch recovery )
The phone restarted after fixing the /data partition, booted up, but hanged after mounting the memory cards and establishing a connection. I had to do a few hard and soft restarts after that, but nothing has been corrupted. It is stable right now on airplane mode, and I'm backing up data via KIES. I think I'll do a factory reset later and restart from scratch.
In summation, your trick worked, and it should be recommended as the first thing one tries. Thanks again!
I have this problem
terminator_5505 said:
this also happen when the battery is completely empty and the phone perform unclean shutdown this is why you must stop using your phone at 1% battery to prevent this stupid bootloop
Click to expand...
Click to collapse
Hi !
I have this problem with my Note and couldn't find a topic explaining how to get out of this loop (in this particular case).
Do you know one or what to do?
I'm JB (I don't know my baseband but it's the official one I got OTA in France, couldn't find it on sammobile). I didn't do anything since the update a few month ago.
I still have the download mode and the recovery menu
Can I wipe securely on JB?
I have retired my original Note N7000 and moved on to Note 3 N9005, so my memory might be a bit rusty.
If you have all original firmware on your Note, I think it would be safer to first flash in PhilZ's safe kernel (http://forum.xda-developers.com/showthread.php?t=1901191) on the device before wiping to avoid the brick bug.
You can then do the wipe from the recovery menu.
If you have some data you need to recover from the device, maybe you can give the method described in the original post to check for filesystem errors and have your Note out of the bootloop.
Good luck.
thanks a lot Mannn :good:
you just save me from reinstalling from scratch
at my i9000,
What I do:
1) Any kind of wipe
2) at Settings: Uninstalling each application.
3) Delete mounted card.
Result after reset:
Everything comes back like I didn't delete anything.
What i tried to do:
Install other ROM, the only one that works is: I9000XXJVU_I9000OXAJVU_OXA (ROM and root package)
Result is the same as before, the only change I have is that after boot I have new system setup wizard that I can't exit from but after hitting reset.
after that reset I have the same problem as before installing the new ROM.
I tried to do the external sd card swap with the vold.fstab, It didn't work, when i try to install the ICS zip file, after reboot install is looping (I see each reboot red lines but it's too fast to read.
another thing that I tried is that hard factory rest: *somenumber*somenumber#
resulted in getting the ....mmcblk0p2 ....stl11 ...stl10 red line format fail
*******************************************************************************************
another thing that I tries is this concept rootzwiki.com/topic/33743-external-sd-card-only-guide/ without taking out the internal sdcard out from my board (maybe i'll do it as a really last resort)
********************************************************************************************
I think that and hope that i was clear enough about the problem and what I did.
Any suggestions?
thanks